Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Get media

wordpress_get_media
Read-only

Retrieve detailed metadata for a WordPress media item, including URLs, dimensions, and MIME type, to inspect attachments by site and media ID.

Instructions

[UNIFIED] Get detailed information about a media item. Returns full metadata including URLs, dimensions, and MIME type.

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

Input Schema

NameRequiredDescriptionDefault
siteYes
media_idYes

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

B3.2/5.0
Behavior3/5

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

The readOnlyHint=true annotation already establishes this is a safe, non-mutating read, so the description's main added value is disclosing the returned metadata fields. It does not cover behavior on a missing or invalid media_id (error vs empty), permission requirements, or whether the response is cached — gaps that matter for a lookup-by-ID tool.

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?

Two tight sentences with the purpose front-loaded and the return contents immediately after; nothing is padded. The "[UNIFIED]" prefix is cosmetic noise but costs little.

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?

For a simple two-parameter read this is close to adequate: the annotations cover safety and the description covers what comes back. However, with no output schema and zero parameter documentation, an agent still lacks the input formats and error behavior needed to call it confidently.

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% for two required parameters, so the description carries the full burden and fails it: neither "site" (site identifier/URL format) nor "media_id" (where the ID comes from) is explained anywhere. The only hint is the phrase "a media item," which weakly implies an ID-based lookup.

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 states a specific verb and resource ("Get detailed information about a media item") and adds what the response contains: URLs, dimensions, and MIME type. It clearly reads as a single-item fetch rather than a list or mutation, though it never names a sibling such as wordpress_list_media to make the distinction explicit.

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?

Usage is only implied: an agent can infer this is the tool for one specific media item when it already has an ID. There is no explicit contrast with wordpress_list_media (browsing) or wordpress_update_media (mutating), and no stated prerequisites such as needing a valid media_id from a prior lookup.

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