Tanod MCP server

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

image_strip_metadata

Idempotent

Strip EXIF, GPS, XMP, IPTC and comment metadata from images to protect privacy. Returns the image without metadata, with pixel data unchanged for JPEG, PNG, WebP and GIF.

Instructions

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

TableJSON 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): 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.	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

TableJSON Schema

Name	Required	Description
`url`	No
`bytes`	No
`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
`source`	No
`removed`	No
`kept_icc`	No
`lossless`	No
`final_url`	No
`operation`	No
`expires_at`	No
`source_url`	No
`after_bytes`	No
`data_base64`	No
`before_bytes`	No
`content_type`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Far exceeds the annotation bar: it discloses per-format lossless vs re-encode behavior, that EXIF rotation is baked into pixels before stripping, a re-check pass, refusal conditions (>40 MP, unsupported formats), a 413 threshold, non-charging on failure, pricing, per-IP free quota, retention/logging policy, and typical latency. Annotations only cover the safety profile (readOnly false, idempotent true, destructive false), so this depth is net-new.

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?

Purpose is front-loaded and every clause carries operational information (limits, formats, cost). It is dense to the point of being a single run-on block, which slightly hurts scanning, but there is little pure 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?

For a stateless transform with an output schema present, the description covers everything an agent needs: accepted inputs, failure modes, billing, limits, retention, and the read/write sibling distinction. No material gap remains.

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 adds meaning by tying auto_orient=false to whether the rotation is baked and by characterizing output="url" as keeping the file out of the context window. It adds useful cross-parameter semantics beyond the already-strong schema descriptions.

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 resource (image metadata) with an explicit enumeration of what is removed (EXIF, GPS, XMP, IPTC, comments, text chunks). It also distinguishes itself from its sibling by naming image_metadata for the read case, so an agent can route correctly 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?

Explicitly directs the reader to image_metadata when the goal is reading metadata, which is a genuine when-to-use-this-vs-alternative signal. It stops short of enumerating the broader sibling set (image_compress, image_convert), but the one true overlap is handled cleanly.

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

Deploy Server