Skip to main content
Glama
@cmssy/mcp-server

@cmssy/mcp-server

Official

Delete media

delete_media
Destructive

Move media assets to the trash for 30-day restoration; assets still in use are refused unless force is set, and unknown IDs are skipped.

Instructions

Move media assets to the trash. They can be restored in the cmssy admin for 30 days, after which they are deleted permanently. Assets still in use are refused unless force is set. Ids not found in this workspace are skipped, so compare deleted 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": "delete_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
idsYesThe asset ids to delete, from list_media. At most 100 per call.
forceNoWhen true, also trash assets that pages, records or branding still reference; those references lose the file until it is restored. The refusal names those files. Requires the media:force-delete permission.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.73.2

TDQS

A4.3/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, it discloses the 30-day restore window, permanent deletion afterwards, partial-success semantics (unknown ids are skipped, not errors), and that force bypasses reference checks and drops the files from referencing pages. That is exactly the extra behavioral context annotations cannot express.

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?

Four short sentences, front-loaded with what happens to the assets, then the restore window, then the failure/override rule, then the partial-success caveat. Every sentence carries actionable information with no filler.

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?

For a destructive two-parameter tool with no output schema, the description covers reversibility, permanent-deletion timing, refusal conditions, the force escape hatch, permission implications, and how to detect skipped ids. An agent has everything needed to call it and interpret the result safely.

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 schema already explains ids limits and force's permission requirement and consequences, so the description adds little new parameter meaning. Its main addition is result-interpretation guidance ("compare deleted with requested"), which is about the response rather than the parameters.

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?

"Move media assets to the trash" gives a specific verb and resource, and the restore/permanent-deletion note clarifies that this is a soft delete rather than an irreversible purge. It does not explicitly name sibling scope boundaries (e.g., folder deletion vs. restore_media), so it stops short of a 5.

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 description states the conditions under which the call fails and when force is appropriate ("Assets still in use are refused unless force is set"), which is real when-to-use guidance. It does not point to named alternatives such as restore_media or delete_media_folder, leaving routing to inference.

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