transkribus_coll_create_doc_from_iiifCreate a document in a specified collection from an IIIF manifest URL, optionally linking a canvas filename reference to import IIIF content.
Create a document in a collection from an IIIF manifest URL.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | IIIF manifest URL | |
| collId | Yes | Collection ID | |
| canvasFilenameReference | No | Canvas filename reference |
Changes observed during successful MCP inspections.
v4.0.0Input schema / properties / canvasFilenameReferenceAdded value: +{
+ "description": "Canvas filename reference",
+ "type": "string"
+}Input schema / properties / fileNameRemoved value: -{
- "description": "File name for the document",
- "type": "string"
-}Input schema / properties / titleRemoved value: -{
- "description": "Document title",
- "type": "string"
-}v3.1.0v3.0.0v2.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover safety (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true), so the bar is lower, but the description adds nothing beyond restating the operation. It does not say the tool fetches an external manifest, whether the resulting document contains pages, or whether repeated calls create duplicates (notably relevant given idempotentHint=false).
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler or redundancy. It is efficient, though its brevity is partly the source of the missing usage and behavior detail.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a non-idempotent, open-world creation tool with no output schema, the description leaves the agent without the returned identifier, any indication of whether the imported manifest is fetched synchronously, or permission/collection-membership prerequisites. The schema covers inputs, but key behavioral expectations are missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and all three parameters (url, collId, canvasFilenameReference) are documented in the schema. The description adds no extra meaning, such as URL format requirements or what the optional canvasFilenameReference does, so baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Create), resource (document), container (in a collection) and source (IIIF manifest URL). The IIIF qualifier implicitly distinguishes it from siblings such as transkribus_coll_create_doc_from_mets, _from_mets_url and _from_ftp, though no sibling is named explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no explicit when-to-use guidance or exclusion criteria. An agent must infer from the name that this is the IIIF variant versus the METS/FTP siblings; the description never says to prefer this tool when the source is an IIIF manifest rather than another import format.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.