mcp_delete_media
Delete a specific media item from WordPress. Optionally force permanent deletion with the force flag.
Instructions
Delete a media item
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Media ID | |
| force | No | Permanently delete |
Delete a specific media item from WordPress. Optionally force permanent deletion with the force flag.
Delete a media item
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Media ID | |
| force | No | Permanently delete |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It only says 'Delete a media item' without explaining behavior like whether deletion is permanent or reversible. The 'force' parameter suggests permanent deletion, but description does not clarify default behavior or consequences.
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?
Very concise single sentence, but lacks detail that could be provided without becoming verbose. Could be improved by adding key behavioral info.
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 tool with no annotations and 2 parameters, description is minimal. Does not explain effect of 'force', return value, or error cases. Incomplete for reliable use by an agent.
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 has 100% coverage, description adds no extra meaning beyond the schema descriptions. Baseline 3 is appropriate.
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?
Description clearly states action (delete) and resource (media item). However, there is a sibling tool 'wp_delete_media' with identical purpose, and the description does not distinguish between them, slightly reducing clarity.
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?
No guidance on when to use this tool versus alternatives like 'wp_delete_media' or 'mcp_bulk_delete_media'. No mention of prerequisites or conditions for safe use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/cvrt-jh/wordpress-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server