Remove a media item by numeric ID from RedStudio. Pages that reference its URL will display a broken asset afterward.
Delete a media item by id. Pages referencing its URL will show a broken asset.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Numeric id |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so the description carries the burden; it discloses a real side effect (broken assets on pages referencing the URL), which is valuable beyond structured fields, though it doesn't mention irreversibility or permissions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, front-loaded with the action and followed by the key consequence; no wasted words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a single-param destructive tool with no output schema, the description covers the core action and a major side effect, but omits whether the deletion is permanent/reversible or requires permissions.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema already documents the id parameter; the description adds no syntax or format details beyond repeating 'by id'.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb 'Delete' and resource 'a media item by id', clearly distinguishing it from siblings like upload_media and list_media.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Implied usage from the verb and resource, but no explicit when/when-not or alternatives (e.g., no mention of deleting vs. replacing media).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.