Skip to main content
Glama

Convert a file

convert

Converts a file to another format and returns a download link (valid 6 hours). The file comes from "url" (a direct link or a Google Drive, Dropbox or OneDrive share link), "uploadId" (from create_upload) or "contentBase64" with "fileName" (files up to 8 MB). Uses credits from the user's converter.studio account; goes ahead on its own up to maxCredits. Waits up to 100 seconds; if not done, call get_conversion.

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": {
      "to": "<to>"
    },
    "name": "convert"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget format id, e.g. "pdf", "mp4", "jpg"
urlNoA link to the file
optionsNoOptional settings (quality, resolution, bitrate…) where the conversion has them
fileNameNoThe file name, needed with contentBase64
uploadIdNoAn upload slot id whose file was uploaded
maxCreditsNoGo ahead without asking up to this price (default 20; 0 only prices it)
contentBase64NoThe file itself, base64 (up to 8 MB)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare the mutation profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), and the description adds substantial behavior on top: credit consumption tied to the account, autonomous spend cap via maxCredits, the 100-second wait, and a 6-hour link lifetime. That is exactly the kind of cost/timeout context an agent needs before invoking an external, credit-charging operation.

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?

Three dense sentences with zero filler, front-loading the action and result before the input sources, cost model and timeout. Every clause carries operational information.

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

Completeness5/5

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

For a 7-parameter conversion tool with nested options and no output schema, the description still covers return value (download link plus validity), input sourcing, cost behavior, and async continuation. Nothing an agent needs to invoke it correctly is missing.

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 baseline is 3, but the description earns above baseline by expanding 'url' to include Google Drive, Dropbox and OneDrive share links, tying uploadId to create_upload, and pairing contentBase64 with fileName and the 8 MB cap. It clarifies maxCredits autonomy (default 20; 0 only prices it) rather than merely restating the field.

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 ("Converts a file to another format") plus the observable outcome ("returns a download link (valid 6 hours)"). It clearly distinguishes itself from siblings by pointing at create_upload as the source of uploadId and get_conversion as the async follow-up.

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?

Gives concrete context for choosing paths: three input sources for the file, and an explicit fallback ("if not done, call get_conversion"). It stops short of stating when not to use this tool or which of the three input methods to prefer.

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.