Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Update media

wordpress_update_media
Destructive

Update WordPress media metadata—including title, description, slug, alt text, caption, status, and associated post—to keep attachments accurate and organized.

Instructions

[UNIFIED] Update media metadata. Supports title, description, slug, alt text, caption, status, and associated post.

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_update_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
postNo
siteYes
slugNo
titleNo
statusNo
captionNo
alt_textNo
media_idYes
descriptionNo

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.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is known. The description adds nothing on top: it does not say whether omitted/null fields are cleared or left untouched, whether the change is reversible, what permission level is required for the target site, or what happens to the attached file. For a destructive mutation with nine parameters and 0% schema coverage, this is a real gap.

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?

Two short sentences, front-loaded with the verb and resource, with no filler or restated title. Nothing could be removed without losing content.

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?

For a nine-parameter destructive mutation with no output schema and no field documentation in the schema, the description is thin. An agent still lacks the semantics of the null defaults, valid status values, and the meaning of site/media_id, all of which it needs to invoke the tool safely.

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 0%, so the description must carry parameter meaning, and it does map field names to concepts – notably 'associated post' for `post` and 'alt text' for `alt_text`. However, it leaves `site` and `media_id` unexplained, gives no accepted values for `status`, and never clarifies what the null defaults mean on update.

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: update media metadata, with an enumeration of the editable fields. The word 'metadata' usefully distinguishes this from siblings that replace or delete media files (wordpress_delete_media, wordpress_upload_media_from_url). It does not name a sibling explicitly, so it stops short of a 5.

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 when-to-use guidance: nothing says when to edit metadata here versus using wordpress_bulk_update_meta or the bulk media tools, and no prerequisites are stated. The [UNIFIED] prefix hints at an umbrella operation but never explains what that means for the caller.

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