Iminify

Create a zip

create_zip

One download address for a zip of the optimized copies of several finished images, by their ids or by a page scan's id. A scan's zip keeps each image in the folders of its address on the page and adds manifest.csv, mapping each address it fetched to its file. Images that have not finished are left out and listed. The address works without a token and expires after an hour. For a single image, get_image's optimized.download_url downloads it directly.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ids`	No	Up to 150 image ids, as compress_images, get_image and list_images return them. Send this or scan_id, not both.
`scan_id`	No	The id scan_page returned, to zip every finished image that scan found. Send this or ids, not both.

Output Schema

TableJSON Schema

Name	Required	Description
`images`	No	How many images the zip holds.
`left_out`	No	The ids of the images left out because they had not finished.
`expires_at`	No
`download_url`	No	Works without a token until expires_at.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "download_url": {
+      "description": "Works without a token until expires_at.",
+      "type": "string"
+    },
+    "expires_at": {
+      "type": "string"
+    },
+    "images": {
+      "description": "How many images the zip holds.",
+      "type": "integer"
+    },
+    "left_out": {
+      "description": "The ids of the images left out because they had not finished.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "type": "object"
+}

Changed2 schema fields changedSep 24, 2026

changedInput schema / properties / ids / description

Previous value: -"The images, by id, up to 150. Send this or scan_id."New value: +"Up to 150 image ids, as compress_images, get_image and list_images return them. Send this or scan_id, not both."

changedInput schema / properties / scan_id / description

Previous value: -"A page scan's id, to zip every finished image it found. Send this or ids."New value: +"The id scan_page returned, to zip every finished image that scan found. Send this or ids, not both."

First observedSep 24, 2026

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial context beyond the annotations: the returned address requires no token, expires after an hour, unfinished images are silently excluded but reported, and scan zips preserve page folder structure plus a manifest.csv mapping addresses to files. Expiry and no-auth behavior are exactly the traits an agent cannot infer from readOnlyHint=false / destructiveHint=false.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Four sentences, each carrying distinct load: what it returns, how scan zips differ, partial-completion behavior, and the auth/expiry traits, closing with the single-image alternative. Front-loaded with the core purpose and no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return shape need not be restated; the description still covers the things the schema cannot — tokenless URLs, one-hour expiry, incomplete-input handling, and the manifest.csv side artifact. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds real meaning: only 'finished' images are included, not-yet-finished ones are omitted and listed, and scan zips add manifest.csv and folder structure. That materially enriches what the ids/scan_id parameters actually select.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a zip' / 'one download address for a zip of the optimized copies of several finished images') and immediately scopes it against the single-image case handled by get_image. An agent can distinguish it from siblings like list_images, get_image, or create_upload_link without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear routing — either a list of finished image ids or a page scan's id — and explicitly names the alternative for a single image ('get_image's optimized.download_url downloads it directly'). The ids-vs-scan_id choice is stated but its full semantics are left to the schema, and there is no guidance on error cases or permission prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Iminify tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?