agent-toolbelt

Image Metadata Stripper

strip_image_metadata

Remove EXIF, GPS, IPTC, XMP, and ICC metadata from images to protect privacy before sharing. Strips sensitive data like location coordinates, camera details, and timestamps from JPEG, PNG, WebP, and TIFF files.

Instructions

Strip EXIF, GPS, IPTC, XMP, and ICC metadata from an image for privacy. Use before uploading or sharing images to remove sensitive embedded data like GPS coordinates, camera model, timestamps, and editing history. Accepts base64-encoded JPEG, PNG, WebP, or TIFF. Returns cleaned base64 image with a removal report.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "image": "<image>"
    },
    "name": "strip_image_metadata"
  }
}

Input Schema

Name	Required	Description	Default
`image`	Yes	Base64-encoded image (JPEG, PNG, WebP, TIFF). No data URI prefix.
`format`	No	Output format ('preserve' keeps original)	preserve
`quality`	No	Quality for lossy formats (1-100)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Mar 30, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It effectively discloses what gets destroyed (specific metadata types like GPS coordinates, camera models) and the return format ('cleaned base64 image with a removal report'). It could mention reversibility or size limits, but covers the essential behavioral traits.

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 efficiently cover: 1) core function, 2) usage context, 3) input specification, and 4) output format. No redundant text or tautology—every sentence earns its place with front-loaded value.

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?

For a 3-parameter image processing tool with 100% schema coverage, the description is complete. It compensates for the missing output schema by describing the return value ('cleaned base64 image with a removal report') and covers the privacy use case comprehensively.

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

Parameters3/5

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

Input schema has 100% description coverage, establishing a baseline of 3. The description reinforces the image parameter requirements ('Accepts base64-encoded JPEG, PNG, WebP, or TIFF') but does not add semantic meaning beyond the schema for the 'format' or 'quality' parameters.

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 explicitly states the tool strips 'EXIF, GPS, IPTC, XMP, and ICC metadata' for 'privacy,' using specific verbs and resources. It clearly distinguishes from siblings (financial analysis, text processing, etc.) by specifying image metadata manipulation.

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?

Provides clear contextual guidance: 'Use before uploading or sharing images to remove sensitive embedded data.' While it doesn't explicitly state when NOT to use it or name alternatives, the sibling tools are sufficiently distinct that this contextual signal is adequate for selection.

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