Skip to main content
Glama

media_get_recovery

Unfinished [cvrt] Media records the background runner backs off or skips (needs [cvrt] Media 0.1.1+). Returns { counts: { stuck, waiting }, items } where items list attachment, state (stuck, waiting, due), attempts, retry_after and rows…

Instructions

Unfinished [cvrt] Media records the background runner backs off or skips (needs [cvrt] Media 0.1.1+). Returns { counts: { stuck, waiting }, items } where items list attachment, state (stuck, waiting, due), attempts, retry_after and rows with size, reason, relative path and redacted error. Read-only; retry with media_retry_recovery.

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": {
      "site": "<site>"
    },
    "name": "media_get_recovery"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
limitNoMost attachments listed, 1..500
stateNoWhich records to list, default stuck

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.1

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the read-only nature and a version prerequisite ([cvrt] Media 0.1.1+), which are genuinely useful behavioral facts. It does not address permissions/capabilities required, ordering, or pagination behavior beyond returning counts and items.

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?

Two sentences, front-loaded with the scope and prerequisite, then the return shape. The second sentence is a dense enumeration but every element (counts, item fields, redaction) is informative rather than padding.

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?

There is no output schema, so describing the returned { counts, items } shape is exactly the right compensation, and the version requirement is stated up front. Slightly incomplete on operator prerequisites and ordering, but well matched to a three-parameter read tool.

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 the baseline is 3; the description adds only that the default listing is stuck records and that limit caps listed attachments. Note the description lists a 'due' item state that the state filter enum does not offer, which mildly muddies how the filter maps to results.

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?

The description names the specific resource (unfinished [cvrt] Media records the background runner backs off or skips) and states what the call returns, which is far more specific than the bare name. It also implicitly separates itself from the retry path by pointing at media_retry_recovery, though it never states the verb 'get/list' explicitly.

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?

It gives a clear role statement ('Read-only; retry with media_retry_recovery'), which routes the agent to the mutation sibling when action is wanted. It lacks an explicit exclusion such as when to prefer media_get_stats or media_get_status, but the use condition is clear enough.

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

Deploy Server

Other Tools