Skip to main content
Glama
lucamarien

rawtherapee-mcp-server

by lucamarien

strip_metadata

Remove EXIF metadata from JPEG files losslessly, including GPS and serial numbers. Optionally strip all metadata while preserving orientation and copyright.

Instructions

Strip selected EXIF metadata from an exported JPEG file.

Operates losslessly — only the EXIF APP1 segment is rewritten, the JPEG image data is not recompressed. By default removes GPS and serial numbers. Use strip_all=True to remove everything except orientation (and copyright if keep_copyright=True). Params: file_path, strip_gps, strip_camera_serial, strip_lens_serial, strip_software, strip_owner, strip_all, keep_copyright, keep_orientation, output_path (None = in-place)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYes
strip_gpsNo
strip_camera_serialNo
strip_lens_serialNo
strip_softwareNo
strip_ownerNo
strip_allNo
keep_copyrightNo
keep_orientationNo
output_pathNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

The description transparently explains that the operation is lossless and only rewrites the EXIF APP1 segment. It also clarifies default removals and the effect of 'strip_all'. Without annotations, this fulfills the burden well.

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 concise with no wasted words. The first sentence states the core purpose, followed by technical details and parameter listing in a logical order.

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 existence and the complexity of 10 parameters, the description covers the main functionality, lossless behavior, and parameter interactions. It lacks explicit mention of error handling or file existence prerequisites but is largely sufficient.

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 description lists all parameters and explains the behavior of key ones like 'strip_all' and 'output_path'. With 0% schema description coverage, it adds meaningful context beyond the schema defaults and types.

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 verb 'strip' and the resource 'EXIF metadata from an exported JPEG file', making the purpose unambiguous. It also distinguishes itself from siblings like 'read_exif' and 'set_metadata' by focusing on removal.

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?

The description provides clear guidance on default behavior and how to use parameters like 'strip_all' and 'keep_copyright'. However, it does not explicitly state when not to use this tool or mention alternatives like 'inspect_metadata' for viewing metadata.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lucamarien/rawtherapee-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server