Skip to main content
Glama

update_media

DestructiveIdempotent

Updates WordPress media metadata—title, alt text, caption, and description—and can attach the media item to a post. Use it to correct or enrich existing media details.

Instructions

Update WordPress media metadata (title, alt text, caption, description)

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

Input Schema

NameRequiredDescriptionDefault
postNoPost ID to attach media to
titleNoMedia title
captionNoMedia caption
alt_textNoAlternative text for accessibility
media_idYesMedia ID to update
descriptionNoMedia description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already mark this as a mutating, idempotent, and notably destructive operation, but the description adds nothing beyond them. It does not say that existing metadata values are overwritten, whether omitted fields are left untouched, or what permissions are needed — the details most relevant given destructiveHint=true.

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 a clear verb-resource framing. The parenthetical field enumeration is partly redundant with the schema, but it is short and not harmful.

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

Completeness3/5

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

With no output schema, full parameter documentation, and annotations covering safety flags, the description is minimally sufficient to identify the tool. However, for a destructive mutation tool it omits partial-update semantics and overwrite behavior, leaving meaningful gaps.

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 description coverage is 100%, so the schema already documents all six parameters, including the 'post' attachment parameter that the description never mentions. The parenthetical field list merely echoes schema property names without adding format, constraints, or semantics, 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?

The description names a specific verb (update) and resource (WordPress media metadata) and enumerates the updatable fields, so an agent can distinguish it from siblings like update_post or delete_media. It stops short of explicitly routing the agent away from adjacent tools such as set_featured_image or upload_media.

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 statement of when to use this tool versus alternatives, no prerequisites (e.g., media must already exist, requires authentication/editor capability), and no note about when a different tool like upload_media or set_featured_image would be appropriate. The agent must infer all usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.