Skip to main content
Glama

convert_image

Convert images between PNG, JPEG, WebP, and AVIF formats with quality and compression presets. Standardize batches and reduce file size without AI processing.

Instructions

Convert images between formats without AI processing.

Use this when:

  • Converting image format (PNG to WebP, JPEG to PNG, etc.)

  • Optimizing file size with compression settings

  • Batch format standardization

NOT for:

  • AI-powered image generation (use generate_image instead)

  • Content modification with AI (use edit_image instead)

Example: "Convert photo.png to WebP format with 80% quality"

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": {
      "inputPath": "<inputPath>",
      "outputFormat": "<outputFormat>",
      "stripMetadata": "<stripMetadata>"
    },
    "name": "convert_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
qualityNo
fileNameNo
inputPathYes
outputFormatYes
stripMetadataYes
compressionPresetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.2

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden, and it leaves out the behaviorally important facts: whether the source file is overwritten or a new file is written, where output lands, and that metadata is stripped by default. 'Without AI processing' is a useful hint about determinism, but a file-mutating tool with zero annotation coverage needs more than that.

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 one-line purpose followed by scannable when/not-for bullets and a concrete example. Slightly padded by the example line, but each section maps to a real decision an agent must make.

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

Completeness2/5

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

For a 6-parameter, 3-required file mutation tool with no annotations and no output schema, the definition covers only routing and intent. The agent still does not know output location, overwrite semantics, or how compressionPreset and quality interact, which are needed to invoke it correctly.

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

Parameters2/5

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

Schema coverage is 0% across 6 parameters, so the description must explain them and it does not. It alludes to quality ('80% quality') and compression presets, but inputPath, fileName, outputFormat's allowed values, and the required stripMetadata default of true go entirely unaddressed in prose.

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 and resource ('Convert images between formats') plus a distinguishing qualifier ('without AI processing') that separates it from generate_image and edit_image. An agent can identify the tool's role without opening the 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?

Provides an explicit 'Use this when' list of three concrete scenarios and a 'NOT for' section naming the two sibling alternatives with the condition that selects them. Nothing about routing is left to inference.

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