Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Delete media

wordpress_delete_media
Destructive

Delete WordPress media library items by ID, choosing to move them to trash or permanently remove them.

Instructions

[UNIFIED] Delete media from library. Can permanently delete or move to trash.

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": {
      "site": "<site>",
      "media_id": "<media_id>"
    },
    "name": "wordpress_delete_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
forceNo
media_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description does add value by disclosing the two outcome modes (trash versus permanent deletion), which annotations cannot express, but it never explains what triggers each mode, what happens to media still attached to posts, or whether the operation is recoverable.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action, with no wasted prose. The unexplained "[UNIFIED]" tag is the only element that does not earn its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive mutation with no output schema and 0% schema coverage, the description is far too thin. It omits the force-to-mode mapping, permission requirements, error behavior for missing media IDs, and consequences of permanent deletion — all things an agent must know before invoking an irreversible operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description carries the full burden and mostly fails: it never names `force` or states that force=true causes permanent deletion and force=false (the default) moves to trash. `site` and `media_id` receive no explanation at all, leaving their expected format and scoping unstated.

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?

The description gives a specific verb and resource: "Delete media from library", which is unambiguous about the operation. It does not differentiate from the sibling wordpress_bulk_delete_media, and the "[UNIFIED]" prefix is unexplained jargon, but an agent knows what this tool does.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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 versus wordpress_bulk_delete_media or the WooCommerce variant, and no stated preconditions such as required permissions or whether attached/in-use media can be deleted. The only hint of choice — permanent delete versus trash — is stated as a capability, not as a rule for selecting it.

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