Convertr file converter

Get a conversion

get_conversion

Read-onlyIdempotent

Get the status of a conversion by id. With wait_seconds (max 80) it waits until the conversion ends. When succeeded, the answer contains the download_url. Needs an API key.

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": {
      "id": "<id>"
    },
    "name": "get_conversion"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	conversion id from convert_file
`wait_seconds`	No	seconds to wait for the result, 0 to 80. Default 0 (return the status at once).

Output Schema

Name	Required	Description
`id`	Yes	conversion id
`error`	No
`input`	No
`output`	No
`status`	Yes	queued, processing, succeeded or failed
`progress`	Yes	progress in percent
`created_at`	No
`finished_at`	No
`credits_charged`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Beyond the readOnly/idempotent annotations, it discloses that waiting blocks until the conversion ends, caps the wait at 80 seconds, that a succeeded result carries a download_url, and that an API key is required. It does not mention failure/error statuses or what a non-terminal response looks like, so it is strong but not exhaustive.

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 short sentences, front-loaded with the core action, then the waiting behavior, then the auth requirement. No filler or redundancy.

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?

With an output schema present, return values need not be explained, yet the description still flags download_url on success and the API key requirement. Only the handling of failed or still-running conversions is left unspecified.

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

Parameters3/5

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

Schema coverage is 100%, so both parameters are already documented, including the 0–80 range and default of 0. The description only restates the max wait and adds that waiting yields an end state, which is marginal value over the schema.

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?

"Get the status of a conversion by id" gives a specific verb (get) plus resource (conversion status), clearly distinct from convert_file and delete_conversion in the sibling list. It stops short of explicitly naming alternatives, but the retrieval framing is unambiguous.

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?

The description implies the key usage decision — call without wait_seconds to poll, with wait_seconds to block until completion — but never states when to prefer one mode or when to use list/delete siblings instead. Usage is inferable rather than explicit.

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

All Convertr file converter tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?