wordpress_bulk_delete_mediaDelete multiple media files in bulk to clean up your WordPress media library quickly. Remove unnecessary images and videos with a single command.
Delete multiple media files
| Name | Required | Description | Default |
|---|---|---|---|
| mediaIds | Yes |
Changes observed during successful MCP inspections.
v1.0.0Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / additionalPropertiesAdded value: +falseDoes the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of disclosing behavioral traits. While 'delete' clearly indicates destruction, it does not state irreversibility, potential impact on posts using the media, or any safety caveats. This is insufficient for a destructive operation with no annotation support.
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?
The description is a single, concise sentence with no waste. It is appropriately short for the limited information it provides, though it lacks the structural detail that would make it fully effective.
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 delete operation with no annotations, no output schema, and a single under-explained parameter, the description is severely incomplete. It does not specify return values, error handling, permanence, or usage context, making it inadequate for an agent to invoke confidently.
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?
The input schema has 0% description coverage and only one parameter, 'mediaIds'. The description does not explain what 'mediaIds' should contain (e.g., array of integers, UUIDs), its format, or any constraints, leaving the agent to infer from the parameter name alone. The description fails to compensate for the low schema coverage.
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 'Delete multiple media files' clearly states the verb (delete), resource (media files), and the bulk aspect ('multiple'), which distinguishes it from the singular delete_media sibling. However, it does not elaborate on exactly how the deletion occurs (e.g., by an array of IDs), so it is specific but not fully detailed.
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?
There is no guidance on when to use this tool versus the singular delete_media or other bulk alternatives. The description does not mention scenarios, prerequisites, or exclusions, leaving the agent without adequate selection cues beyond the name.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.