Skip to main content
Glama

Convert an image to another format

convert_image

Convert an image to JPEG, PNG, WebP, AVIF, GIF or TIFF. Use webp or avif to modernise images for the web. Returns a download URL valid for one hour.

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": {
      "format": "<format>"
    },
    "name": "convert_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatYesThe format to convert to.
qualityNo
image_urlNoPublic http(s) address of the image. Use this or image_base64.
max_widthNo
max_heightNo
image_base64NoThe image file's bytes, base64-encoded. Use for a local file, e.g. one in the repository.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, which raises the question of what side effect occurs; the description answers it partially by disclosing the output contract: 'Returns a download URL valid for one hour.' That TTL is valuable behavioral context an agent cannot get from annotations or schema. It does not clarify that the original image is untouched (relevant given readOnlyHint=false) or how animated inputs are handled, keeping it short of a 5.

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?

Three short sentences, front-loaded with the capability and ending with the return contract. No redundant restatement of the title or schema. The middle sentence is purpose-serving rather than filler.

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

Completeness3/5

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

For a 6-parameter, non-readonly tool with no output schema, the description covers the return artifact and its expiry but leaves three undocumented parameters (quality, max dimensions) unexplained, despite one of them controlling output fidelity. An agent could call it for the required format only, but not intelligently tune the conversion.

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 description coverage is only 50%: quality, max_width and max_height have no description in the schema, and the description mentions none of them, so resizing and compression behavior is entirely undiscoverable from text. The description's format list also fails to reflect the full enum, adding nothing beyond what the schema already enumerates. Only the input-source choice is even indirectly implied by the topic.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource: 'Convert an image to JPEG, PNG, WebP, AVIF, GIF or TIFF.' An agent immediately knows this is a format conversion tool, distinct from siblings like compress_image or upscale_image. Minor deduction because the format list is a partial subset of the 12-value enum in the schema (bmp, ico, jxl, pdf, tga and psd are omitted), so the description slightly under-represents capability.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It gives one concrete recommendation — 'Use `webp` or `avif` to modernise images for the web' — which is genuine when-to-use guidance for format choice. However, there is no guidance on when to reach for this tool instead of compress_image, upscale_image, inspect_image, or remove_background, nor any prerequisites such as accepted source formats or size limits.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources