delete_mediaDelete a specific media item from your social media library using its unique media ID. Clean up unwanted or outdated media to keep your content organized.
Delete one media item.
| Name | Required | Description | Default |
|---|---|---|---|
| mediaId | Yes |
Changes observed during successful MCP inspections.
v0.1.2Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states the action with no mention of permanence, irreversibility, permissions, or effects on associated data, leaving the destructive nature implied by the verb alone.
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?
A single sentence with no filler. The core action and scope are front-loaded, and every word contributes to the meaning.
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 one-parameter deletion tool this is nearly adequate, but without annotations or an output schema the agent is left to infer success/error behavior and whether deletion is permanent. It also does not point to related tools for discovering mediaId.
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 description coverage is 0%, and the description does not explain mediaId's format, origin, or how to obtain it. The parameter name is somewhat self-explanatory, but the description adds no semantic value beyond the schema.
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?
The description uses a specific verb ('Delete') and resource ('one media item'), clearly distinguishing this from delete_media_many (one vs many) and from media-read/upload tools. The singular scope is explicit and unambiguous.
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?
The description implies singular use with 'one media item,' but it does not explicitly reference alternatives such as delete_media_many or clarify when this tool should be chosen over them. Guidance is present only by implication.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.