Skip to main content
Glama

wp_delete_media

Permanently deletes a WordPress media item and its associated files using the site and media ID.

Instructions

Delete a media item and its files

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>",
      "id": "<id>"
    },
    "name": "wp_delete_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMedia ID
siteYesSite id (see list_sites)
forceNoPermanently delete; media cannot be trashed unless MEDIA_TRASH is on, so false usually fails with 501

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.14.0
    • changedInput schema / properties / force / description
      Previous value: -"Permanently delete (bypass trash)"New value: +"Permanently delete; media cannot be trashed unless MEDIA_TRASH is on, so false usually fails with 501"
    • changedInput schema / properties / id / type
      Previous value: -"number"New value: +"integer"
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "id"
      -]New value: +[
      +  "site",
      +  "id"
      +]
  3. First observedv2.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. 'And its files' hints that attachments are removed from storage, but it never says the operation is irreversible, never mentions permission requirements, and never addresses the force semantics that the schema flags as failure-prone.

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?

A single front-loaded sentence with zero filler, which is the right shape. It is arguably too terse for a destructive operation, but there is no wasted wording to penalize.

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

Completeness2/5

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

This is a destructive mutation with no annotations and no output schema, yet the description spends one short clause on it. Nothing explains the irreversibility or the common 501 outcome that the schema warns about, leaving the agent under-informed for a high-consequence call.

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

Parameters3/5

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

Schema coverage is 100%, so the meaning of site, id, and force is already fully documented, including the 501 failure note. The description adds only the implicit link between 'its files' and permanent deletion, so the baseline of 3 applies.

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?

States a specific verb and resource ('Delete a media item') and adds scope detail ('and its files') that distinguishes it from a plain record deletion. It does not name siblings such as mcp_delete_media or mcp_bulk_delete_media, so differentiation is only partial.

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 mcp_delete_media, mcp_bulk_delete_media, or wp_update_media, nor any preconditions (e.g., that the item should already be identified via wp_list_media). The agent must infer the choice from the name alone.

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