Gemini Executive Synthesis

Automation API (MCP) accuracy, specifically tool metadata regarding file system operations.

Technical Positioning

Reliable and transparent automation capabilities, consistent with Adobe Acrobat's enterprise-grade features.

SaaS Insight & Market Implications

This printcraft automation bug, where file-writing MCP tools incorrectly advertise readOnlyHint: true and destructiveHint: false, is a severe transparency and reliability issue. Clients relying on the MCP tools/list for accurate metadata will receive misleading information about filesystem side effects, potentially leading to data loss or unexpected behavior in automated workflows. For an Acrobat alternative, robust and truthful API annotations are fundamental for enterprise integration and developer confidence. This flaw directly undermines the trustworthiness of printcraft's automation capabilities, significantly hindering its adoption in environments requiring precise control and predictability over document processing operations.

Proprietary Technical Taxonomy

Raw Developer Origin & Technical Request

GitHub Issue Oct 7, 2026

Repo: storytold/printcraft

fix(automation): file-writing tools advertise read-only MCP annotations

## Summary

`doc_export_data`, `accessibility_report`, and `image_save` advertise `readOnlyHint: true` through MCP `tools/list`, but each writes to its required `path` and replaces an existing file there. All three also advertise `destructiveHint: false`. This contradicts the tool table's definitions of read-only and destructive behavior and gives clients incorrect information about filesystem side effects.

## Runtime or environment

- Latest published release tested: `v0.2.1`, tag commit `dcb00238896e418b357e6dd777ee35bad36f0b97`, using `printcraft-cli-0.2.1-macos-universal.zip`. Its SHA-256 was `bda65829033916c5de5a7ddc0763437f8db2e8792ee43c8dc2676434acb3d495`, matching the release's `SHA256SUMS.txt`. The extracted binary's SHA-256 was `b7783b596870ed5a326f29456d4647382d2e1e4d7b7ffe75ded192cd15b86995` and `--version` reported `printcraft-cli 0.2.1`.
- Host: macOS 27.0.1, Darwin 27.0.0, arm64. Tests used only synthetic data in a disposable directory.
- Current default branch inspected: `main` at `1c78ff479ce5cf5cbcf7af5100378c9311b95162`. The three annotations, MCP mapping, file-writing handlers, and atomic-write helper remain unchanged from the release. This branch was inspected from source, not built or executed. The intervening engine changes concern form check styles and a catalog entry, not these handlers.

## Steps to reproduce

Run the following Python script in a new disposable directory with the tested release's `printcraft-cli` on `PATH`. It creates an original on...

View Raw Source

Developer Debate & Comments

No active discussions extracted for this entry yet.

Adjacent Repository Pain Points

Other highly discussed features and pain points extracted from storytold/printcraft.

text_find does not return occurrences in vertically laid-out text

Extracted Positioning

Text search functionality, specifically for vertically laid-out text (CJK).

Comprehensive text processing capabilities, including accurate search across diverse layouts, matching Adobe Acrobat's functionality.

option for adding signature from image is not present.

Extracted Positioning

Digital signature functionality, specifically image-based signature creation.

Feature parity with Adobe Acrobat for core document interaction and signing workflows.

fix(cli): text exits successfully after a selected-page error

Extracted Positioning

CLI error handling and exit status consistency.

Robust and predictable command-line utility behavior, essential for automation and scripting, mirroring Adobe Acrobat's reliability.

[Bug] Outline/bookmark titles render as mojibake for non-ASCII (CJK) text

Extracted Positioning

PDF rendering fidelity, specifically for non-ASCII text in document outlines/bookmarks.

Accurate display of PDF content across character sets, matching Adobe Acrobat's rendering.

OCR not working on wasm build (v0.2.1)

Frequently Asked Questions

Market intelligence mapped to Automation API (MCP) accuracy, specifically tool metadata regarding file system operations..

What problem does Automation API (MCP) accuracy, specifically tool metadata regarding file system operations. solve?

Based on our AI analysis of the original developer request, its primary technical positioning is: Reliable and transparent automation capabilities, consistent with Adobe Acrobat's enterprise-grade features.

What is the general sentiment around Automation API (MCP) accuracy, specifically tool metadata regarding file system operations.?

Yes, we have tracked 1 direct responses and active debates regarding this specific topic originating from GitHub Issue.

Which technical concepts are associated with Automation API (MCP) accuracy, specifically tool metadata regarding file system operations.?

Our proprietary extraction maps Automation API (MCP) accuracy, specifically tool metadata regarding file system operations. to adjacent architectural concepts including file-writing tools, read-only MCP annotations, doc_export_data, accessibility_report.

Which commercial products utilize Automation API (MCP) accuracy, specifically tool metadata regarding file system operations.?

Yes, market intelligence reveals commercial overlap. A product named 'FetchSandbox MCP' focuses directly on this: The MCP that proves your AI's integration fixes work

Engagement Signals

Replies

open

Issue Status

Cross-Market Term Frequency

Quantifies the cross-market adoption of foundational terms like CLI release and tag commit by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.