Skip to main content
Glama

File Conversion

file-convert
Read-only

Convert documents, web pages, spreadsheets and images between formats. Returns a download URL of the converted file with its name, size and formats. Use to change a file's format, for example Word to PDF or PDF to Markdown. To extract specific fields use documents; to read a web page's text use scrape. Converts pdf to txt, md, html, png, jpg; docx to pdf, txt, md, html; pptx to txt, md; xlsx to csv, json, md, html, txt; csv to xlsx, json, md, html; html to pdf, txt, md; web to pdf, txt, md, html; txt to pdf, html; epub to pdf, txt, md; svg to pdf, png; png to jpg, webp, gif, bmp, tiff, pdf; jpg to png, webp, gif, bmp, tiff, pdf; webp to png, jpg, gif, bmp, tiff, pdf; gif to png, jpg, webp, bmp, tiff, pdf; bmp to png, jpg, webp, gif, tiff, pdf; tiff to png, jpg, webp, gif, bmp, pdf; heic to png, jpg, webp, pdf. Cost: 2 credits, charged only when a call succeeds.

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": {
      "file_url": "<file_url>",
      "source_format": "<source_format>"
    },
    "name": "file-convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_urlYesURL of the file to convert (for source_format web, the page itself).
source_formatYesFormat of the file: pdf, docx, pptx, xlsx, csv, html, web (a page, from its HTML without JavaScript), txt, epub, svg, png, jpg, webp, gif, bmp, tiff or heic.
target_formatNoFormat to convert to: one the source format converts to (the tool's description lists each source's targets). Any other pair is refused with the formats its source converts to.pdf

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / target_format / description
      Previous value: -"Format to convert to. The conversion table's pairs convert in-house; other pairs go to ConvertAPI."New value: +"Format to convert to: one the source format converts to (the tool's description lists each source's targets). Any other pair is refused with the formats its source converts to."
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so credit is for added context, and the description delivers: it discloses the return payload (download URL plus name, size and formats) and a billing rule (2 credits, charged only on success), which annotations cannot convey. It stops short of stating URL lifetime, input size limits, or whether conversion is synchronous, leaving some operational unknowns.

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 correctly: purpose, then a concrete example, then sibling routing, then the compatibility matrix, then cost. The exhaustive format list is long but each entry carries contract information rather than filler; a table would scan better than the semicolon-separated run-on, which is the only structural weakness.

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 conversion tool with no output schema, the description covers purpose, inputs, return shape, cost, and the error behavior for unsupported pairs. Remaining gaps (file size caps, download URL expiry, async behavior for large files) are operational rather than selection-blocking.

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 earns above baseline because the source-to-target matrix is the only place the valid target_format values per source actually live — the schema's target_format description explicitly defers to it. The per-pair enumeration converts an open string parameter into a practically constrained one.

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 a concrete resource set ("Convert documents, web pages, spreadsheets and images between formats") and immediately names the distinct siblings it is not ("documents", "scrape"). An agent can tell what this does and what it doesn't do without opening any 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?

Gives an explicit when-to-use rule ("Use to change a file's format, for example Word to PDF or PDF to Markdown") plus two named alternatives with the condition that selects each: field extraction goes to documents, page-text reading goes to scrape. 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.