Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Restore media

restore_media
Destructive

Restores trashed media assets to their original folder, or to the library root when that folder no longer exists. Accepts up to 100 asset ids and skips ids not in the trash.

Instructions

Restore media assets from the trash. Each returns to its folder, or to the library root when that folder no longer exists (counted in movedToRoot). Ids not in the trash are skipped, so compare restored with requested.

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": {
      "ids": "<ids>"
    },
    "name": "restore_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesThe asset ids to restore, from list_trashed_media. At most 100 per call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say destructive/not-read-only; the description adds real behavior: assets return to their original folder, fall back to library root when the folder is gone (reported via movedToRoot), and non-trashed ids are silently skipped so the caller must reconcile restored vs requested. That partial-success and reconciliation detail is exactly what an agent needs and is impossible to infer from annotations.

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: operation first, then placement semantics, then the failure/reconciliation rule. No filler, no repetition of the title, and the most surprising behavior is stated before the caller acts.

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 no output schema, the description carries return-shape duty and does so by naming the counts (restored, movedToRoot) and the skip case. The exact response field set is only implied rather than enumerated, which is the one remaining gap for a single-parameter mutation tool.

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 already 100% including the maxItems=100 cap and the pointer to list_trashed_media, so the baseline is 3. The description adds meaning beyond the schema by explaining what happens to ids that fail the trash check, which is semantic behavior of the parameter rather than a restatement.

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 ('Restore') plus resource ('media assets') and scope ('from the trash'), which inherently separates it from siblings like restore_page or delete_media. An agent can identify the operation without opening the schema.

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?

The precondition is clear: assets must currently be in the trash, otherwise they are skipped, and it points at the relationship between requested and restored counts. It does not explicitly name an alternative tool or exclusion, but the precondition plus the schema's reference to list_trashed_media gives strong usage context.

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