Skip to main content
Glama

Convert.Online

Convert a file

convert

Convert a file to another format and return a download link. Give it one of: source_url (any URL the server can fetch — the best option when the file is already somewhere reachable) or import_id (from create_upload — the way in for a file on someone's device or in your own sandbox, whatever its size). There is deliberately no way to pass the bytes inline: those calls are relayed and routinely never arrive, leaving the person watching a spinner. Settings such as resizing, quality or codecs go in options — call list_options first to get the exact names for the conversion. Runs against your account and counts toward your quota.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
optionsNoConversion settings, keyed by the option names from list_options — e.g. {"resize_width_image": 1000, "aspect_ratio_image": true}. Names differ per conversion, so do not guess them.
filenameNoFile name of the source, e.g. "photo.jpg". Required with source_base64 unless input_format is given.
import_idNoId returned by create_upload, after the bytes have been PUT to its upload_url. Use this for local files of any size.
source_urlNoURL of the file to convert, fetched by our server. Any link reachable from the internet works, including a temporary or signed URL for a file the user attached to this conversation — prefer this whenever you have such a URL, because nothing about the file has to pass through the conversation itself.
input_formatNoSource format (optional; inferred from the file name or URL).
output_formatYesTarget format, e.g. "jpg", "pdf", "mp3".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that the tool runs against the user's account and counts toward quota, that the server fetches URLs, and that inline byte passing is deliberately unsupported because those calls fail. This adds meaningful behavioral context.

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?

Four sentences, each carrying distinct information: purpose, source selection, a warning about a common failure, and options/quota. It is slightly longer than necessary but every sentence earns its place.

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?

The description covers the main decision points, but it doesn't mention that the conversion may be asynchronous (sibling get_job exists) or that list_formats should be checked for supported output formats. For a 6-parameter tool with no output schema, this is a notable gap.

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 adds value by explaining the selection rule between source_url and import_id, stating that options must come from list_options, and clarifying the deliberate absence of an inline bytes parameter.

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 opens with a specific verb and resource: 'Convert a file to another format and return a download link.' It also distinguishes the tool from siblings by naming create_upload and list_options, making clear what this tool does versus uploading or listing.

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?

The description gives explicit guidance on choosing between source_url and import_id, warns against attempting to pass bytes inline, and instructs the agent to call list_options for exact option names. This is direct, actionable usage guidance.

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