Skip to main content
Glama

media_bulk_restore

Restores the originals of every optimized attachment by running one restore job per file, replacing all optimized files. Requires confirm: true; backups already cleaned up cannot be restored.

Instructions

Restore the originals of EVERY optimized attachment (one restore job each), replacing all optimized files. Large and slow; attachments whose backup was cleaned up cannot be restored. Needs confirm: true, otherwise the site refuses with 400.

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_bulk_restore"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
confirmNoMust be true for the action to run; anything else makes the site refuse it with 400

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does substantial work: it discloses the destructive effect (replacing all optimized files), the one-job-per-attachment fan-out, the cost (large and slow), an irrecoverable case (cleaned-up backups), and the confirm gate with its 400 failure mode. It does not address permissions, rate limits, or whether the operation can be undone, so it falls short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with the action and scope, then cost, then precondition and the confirm requirement. No sentence is filler and each adds a distinct operational fact.

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 an unannotated bulk mutation with no output schema, the description covers the destructive effect, scale, cost, an unrecoverable edge case, and the required confirm flag. It is nearly complete; only permissions/authorization and reversibility are left unstated.

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 description coverage is 100%, and both parameters already document themselves, including confirm's 400 refusal behavior. The description restates the confirm requirement rather than adding new meaning about the parameters, so the baseline 3 applies.

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 gives a specific verb and resource ("Restore the originals of EVERY optimized attachment") plus the key scope cue that it operates on all attachments with one job each, which implicitly separates it from the single-attachment restore sibling. It stops short of naming an alternative tool, so the disambiguation rests on the word "EVERY" rather than an explicit contrast.

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 clearly frames the operational context ("Large and slow") and states a hard precondition: attachments whose backup was cleaned up cannot be restored. It offers no explicit when-not guidance or named alternative such as a single-attachment restore, so the agent must infer the alternative from sibling names.

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