Skip to main content
Glama

Iminify

by com.iminify
OverviewDiscussionsAdmin

Create a zip

create_zip
Read-only

One download address for a zip of the optimized copies of several finished images, by their ids or by a page scan's id. 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
NameRequiredDescriptionDefault
idsNoUp to 150 image ids, as compress_images, get_image and list_images return them. Send this or scan_id, not both.
scan_idNoThe id scan_page returned, to zip every finished image that scan found. Send this or ids, not both.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
imagesNoHow many images the zip holds.
left_outNoThe ids of the images left out because they had not finished.
expires_atNo
download_urlNoWorks without a token until expires_at.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • 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"
+}
  2. Changed2 schema fields changed
    • 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."
  3. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The description adds behavioral details beyond the readOnlyHint: the address works without a token, expires after an hour, and unfinished images are omitted and listed. This is valuable context not in annotations.

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?

The description is two sentences, efficient, and front-loads the core purpose and key constraints (single download vs zip). Every sentence provides useful information.

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

Completeness4/5

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

Given the output schema exists and annotations cover safety, the description covers the essential use case, constraints (mutual exclusivity, expiration, token-free), and exceptions (unfinished images). It does not elaborate on the response format but that's covered by output schema.

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?

The schema covers parameters fully (100%), but the description adds meaning by explaining that ids and scan_id are mutually exclusive and that ids are limited to 150, which is not in the schema descriptions. This adds value.

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?

The description clearly states the tool creates a zip download address for finished images, by ids or scan_id, and distinguishes itself from get_image for single downloads. It is specific and differentiates from siblings.

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?

It explains when to use this tool (for multiple images or all from a scan) and implicitly contrasts with get_image for single images. It doesn't explicitly state when not to use it, but the context is clear.

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

All Iminify toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources