Skip to main content
Glama

get_conversion

Retrieve the full Markdown content of a previously saved conversion by its ID.

Instructions

[deprecated: use search_library/get_library_items] Retrieve the full Markdown content of a previously saved conversion by its ID.

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

NameRequiredDescriptionDefault
idYesThe conversion ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.8.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the deprecation status and that the return is full Markdown content. It says nothing about permissions, scope of access, or whether the content is current, so coverage is partial for a read tool.

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?

One sentence with the deprecation warning front-loaded and the purpose second, which is the correct priority order for a deprecated tool. Nothing in it is filler.

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 one-parameter read tool with no output schema, the description covers purpose, return type, and deprecation routing, which is enough to call it correctly. The only minor gap is that it doesn't indicate what happens if the ID is not found.

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% and the single `id` parameter is already documented as "The conversion ID". The description's phrase "by its ID" restates the schema without adding format, source, or validity details, so the baseline of 3 applies.

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+resource ("Retrieve the full Markdown content of a previously saved conversion") plus the lookup key ("by its ID"), which no sibling tool does. The bracketed deprecation notice up front further disambiguates it from search_library and get_library_items.

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?

Explicitly marks itself deprecated and names the two replacement tools to use instead, giving an unambiguous when-not-to-use rule. An agent reading this knows to route to search_library or get_library_items rather than calling this tool.

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