wpxmcp

Edit a media item (alias)

edit_media

Update existing media items by modifying title, caption, alt text, description, or attaching to a post. Correct or enhance media metadata on WordPress.

Instructions

Legacy alias for update_media, kept for backward compatibility. Prefer update_media.

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

Input Schema

Name	Required	Description
`id`	Yes	The item ID.
`post`	No	Attach to this content ID.
`title`	No	Display title.
`caption`	No	Caption shown beneath the item.
`site_id`	No	Which configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.
`alt_text`	No	Alternative text for accessibility and SEO.
`description`	No	Longer descriptive text.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv2.0.0Sep 15, 2026
- changedInput schema / $schema
```
Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
```
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / id / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / id / minimum
```
Added value: +-9007199254740991
```
- addedInput schema / properties / post / maximum
```
Added value: +9007199254740991
```
- addedInput schema / properties / post / minimum
```
Added value: +-9007199254740991
```
First observedv1.0.0Aug 24, 2026

TDQS

A4/5.0

Behavior3/5

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

The description reveals that this is an alias with legacy status, which is useful context beyond the annotations, but it does not describe side effects, permissions, or what fields actually get modified. Since readOnlyHint=false, destructiveHint=false, and idempotentHint=false already signal a non-read, non-destructive mutation, a mid score is appropriate.

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

Conciseness5/5

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

The description is two short sentences with no filler: it states the alias relationship, the backward-compatibility rationale, and the preference for update_media. Every sentence earns its place.

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

Completeness4/5

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

For a deprecated alias, the description is largely complete because it directs the agent to update_media for canonical behavior, and the input schema documents all parameters. It does not describe return values, but the alias framing makes that omission minor.

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 fully documents all seven parameters and their meanings. The description adds no parameter-level information, 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 title and description make clear this tool edits a media item, and the description explicitly frames it as a legacy alias for update_media. This distinguishes it from update_media and other media tools, though it relies on the referenced tool to fully define the operation.

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

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit routing guidance: this is a legacy alias for update_media, kept only for backward compatibility, and update_media should be preferred. This is a clear when-to-use versus when-not-to-use statement with a named alternative.

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

Deploy Server