Convertr file converter

List supported formats

list_formats

Read-onlyIdempotent

List what Convertr can convert. Without input_format it returns all supported input formats (short list). With input_format (for example mp4) it returns every output format for that input, with its group (Audio, Video, Image, Document ...). Use it to check that a conversion exists before you call convert_file. Works without an API key.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_formats"
  }
}

Input Schema

Name	Required	Description	Default
`input_format`	No	input format to list the possible output formats for, for example mp4

Output Schema

Name	Required	Description
`input`	No	the input format (when input_format was given)
`inputs`	No	all input formats (when input_format was not given)
`outputs`	No	output formats for input (when input_format was given)

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 8, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds genuinely new operational facts: it works without an API key, and the return shape differs by mode (short list vs. grouped output formats). Return details are partly redundant with the existing output schema, which keeps this from 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?

Front-loaded with the purpose, then the two modes, then the usage recommendation, then the auth note—a logical order with no filler sentences. Minor redundancy in restating the mp4 example already present in the schema keeps it just below top marks.

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?

A single optional parameter, full schema coverage, an output schema, and safety annotations mean the description only needs to supply intent, usage routing, and auth context—all of which it does. Nothing an agent needs in order to call this 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 the baseline is 3, but the description goes further by explaining the semantic effect of input_format: it yields every output format for that input, annotated with its group (Audio, Video, Image, Document). That meaning is not captured by the one-line schema description.

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 ("List what Convertr can convert") and immediately distinguishes the two modes of the tool based on whether input_format is supplied. An agent can tell it apart from convert_file without opening either 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: "check that a conversion exists before you call convert_file," naming the sibling it precedes. Both invocation modes and their distinct results are described, so nothing about when to reach for this tool 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.

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?