Tanod Images

imagepeek: strip an image's metadata (EXIF, GPS, XMP)

image_strip_metadata

Idempotent

imagepeek: Strip an image's EXIF, GPS, XMP, IPTC and comment metadata. To read the metadata use image_metadata. Returns the image without EXIF (GPS included), XMP, IPTC, comments and text chunks: JPEG, PNG, WebP and GIF are stripped losslessly at the byte level (pixel data unchanged), TIFF, BMP, ICO and AVIF re-encoded; an EXIF rotation is baked into the pixels first unless auto_orient is false. The result is re-checked to hold no metadata; removed lists what went. Reads PNG, JPEG, WebP, GIF, TIFF, BMP, ICO and AVIF; other formats and images over 40 megapixels are refused (not charged). Output: base64 data_base64, without EXIF, GPS, XMP or IPTC; over 15 MB or 50 megapixels is a 413 (not charged). Images are not logged; a result is kept only with output "url" (24 h). Typically 0.5-2 s. Price: USD 0.002. Free: 3 imagepeek calls per IP per UTC day. Docs: https://tanod.dev/learn/strip-image-metadata-api.html

Input Schema

Name	Required	Description	Default
`url`	No	Public http(s) URL of the image (at most 10 MB; private, internal and IP-literal hosts are refused); or use image_base64.
`output`	No	base64 (default): inline. url: stored for 24 hours; link, metadata.	base64
`keep_icc`	No	Keep the ICC colour profile (default false: removed too).
`auto_orient`	No	Bake a non-1 EXIF orientation into the pixels (re-encode).
`image_base64`	No	The image as standard or url-safe base64 (at most 10 MB decoded; a data:image/...;base64, prefix is fine); or use url.

Output Schema

Name	Required	Description
`url`	No	Public link.
`bytes`	No	Bytes.
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`input`	No
`notes`	No
`width`	No
`format`	No
`height`	No
`method`	No
`sha256`	No	SHA-256.
`source`	No
`removed`	No
`kept_icc`	No
`lossless`	No
`final_url`	No
`operation`	No
`expires_at`	No	UTC expiry.
`source_url`	No
`after_bytes`	No
`data_base64`	No
`before_bytes`	No
`content_type`	No	MIME type.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026

changedInput schema / properties / output / description

Previous value: -"base64 (default): the file comes back inline as base64. url: the file is stored for 24 hours and the reply carries a download link (url, expires_at, bytes, content_type, sha256) instead of the base64, which keeps the file out of your context window."New value: +"base64 (default): inline. url: stored for 24 hours; link, metadata."

addedOutput schema / properties / bytes / description
```
Added value: +"Bytes."
```
addedOutput schema / properties / content_type / description
```
Added value: +"MIME type."
```
addedOutput schema / properties / expires_at / description
```
Added value: +"UTC expiry."
```
addedOutput schema / properties / sha256 / description
```
Added value: +"SHA-256."
```
addedOutput schema / properties / url / description
```
Added value: +"Public link."
```

Changed4 schema fields changedOct 12, 2026

addedInput schema / properties / output

Added value: +{
+  "default": "base64",
+  "description": "base64 (default): the file comes back inline as base64. url: the file is stored for 24 hours and the reply carries a download link (url, expires_at, bytes, content_type, sha256) instead of the base64, which keeps the file out of your context window.",
+  "enum": [
+    "base64",
+    "url"
+  ],
+  "title": "Output",
+  "type": "string"
+}

addedOutput schema / properties / expires_at

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / sha256

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

addedOutput schema / properties / url

Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}

Changed3 schema fields changedOct 8, 2026

addedInput schema / properties / keep_icc / description

Added value: +"Keep the ICC colour profile (default false: removed too)."

changedInput schema / properties / url / description

Previous value: -"Public http(s) URL of the image (at most 10 MB); or use image_base64."New value: +"Public http(s) URL of the image (at most 10 MB; private, internal and IP-literal hosts are refused); or use image_base64."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "after_bytes": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "before_bytes": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "bytes": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "content_type": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "data_base64": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "error": {
+      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
+    },
+    "final_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "format": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "height": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "input": {
+      "properties": {
+        "animated": {
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "bytes": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "format": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "frames": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "has_alpha": {
+          "type": [
+            "boolean",
+            "null"
+          ]
+        },
+        "height": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        },
+        "width": {
+          "type": [
+            "integer",
+            "null"
+          ]
+        }
+      },
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "kept_icc": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "lossless": {
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "method": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "notes": {
+      "items": {
+        "type": [
+          "string",
+          "null"
+        ]
+      },
+      "type": [
+        "array",
+        "null"
+      ]
+    },
+    "operation": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "removed": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "source": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "source_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "width": {
+      "type": [
+        "integer",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

First observedOct 8, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description goes far beyond by disclosing lossless byte-level stripping for JPEG/PNG/WebP/GIF vs re-encoding for TIFF/BMP/ICO/AVIF, that EXIF rotation is baked into pixels, that the result is re-verified, pricing ($0.002), free tier (3/IP/day), timing, non-logging, and the 24 h retention of `url` output. This is a rare level of behavioral detail.

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

Conciseness4/5

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

Front-loaded with purpose and the sibling pointer, then dense but load-bearing facts about formats, limits, and cost. It is long for a single tool, though nearly every clause carries operational information an agent needs; pricing and the docs URL are the only mildly peripheral additions.

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?

Covers inputs accepted, size/MP caps, per-format behavior, the returned field (`data_base64`), error behavior (413, not charged), state persistence, rate limits and cost. Even with an output schema present, nothing an agent needs to invoke or reason about the result 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 coverage is 100%, so the baseline is 3; the description earns above that by explaining the effect of `auto_orient` (rotation baked into pixels unless false), the difference between `output` base64 vs url and its 24 h retention, and the input size limits. `keep_icc` is left to the schema, so it stops short of a 5.

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 (strip) and the exact resources removed (EXIF, GPS, XMP, IPTC, comments), and explicitly distinguishes itself from the sibling image_metadata reader. An agent can tell it apart from every other imagepeek sibling 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 Guidelines5/5

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

Explicitly routes to image_metadata for the inverse operation, and states when the tool refuses work: unsupported formats and images over 40 megapixels, plus the 15 MB / 50 MP output cap. Format-specific behavior (lossless vs re-encode) is also stated so the agent knows the cost of each path.

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

All Tanod Images tools Inspect

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

Need Help?