Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_update_media_metadata

Update media metadata for any WordPress attachment by ID, changing the title, alt text, caption, or description. Set accurate alt attributes to improve accessibility and SEO.

Instructions

Update media title, alt text, caption, or 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": {
      "id": "<id>"
    },
    "name": "wp_update_media_metadata"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
altNo
titleNo
captionNo
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'update' which implies mutation, but says nothing about whether the operation is atomic, whether it overwrites or merges, error handling, return values, or required permissions. This is minimal disclosure.

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 a single concise sentence that front-loads the purpose. Every word is relevant, no redundancy or verbosity.

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?

With 5 parameters, no output schema, and no annotations, the description is too sparse. It does not explain that the id must correspond to an existing media item, what the response looks like, whether all parameters are optional beyond id, or any side effects. Lacks essential context for a mutation tool.

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%, so the description should add meaning beyond parameter names. It merely lists the same field names (title, alt, caption, description) as in the schema, without explaining formats, constraints (e.g., max length), or how they map to WordPress media fields. Adds almost no value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Update' and the resource 'media metadata', listing the specific fields it affects (title, alt text, caption, description). It distinguishes from siblings like wp_update_post or wp_update_page which update different content types.

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

Usage Guidelines3/5

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

The description implies usage for updating media metadata but does not provide explicit guidance on when to use this tool versus alternatives like wp_update_post for post attachments or wp_upload_media for creation. No when-not or alternative tooling is mentioned.

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