Skip to main content
Glama

media_get_attachment

Retrieves a WordPress media attachment's optimization records, job history, and file-replace undo status for auditing or troubleshooting.

Instructions

One attachment: its optimization records, job history and whether a file replace can be undone.

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

Input Schema

NameRequiredDescriptionDefault
idYesAttachment id
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does usefully disclose the payload contents (optimization records, job history, replace-undo feasibility), which is real behavioral information. It does not state whether the call is read-only, what happens when the attachment is missing, or what output shape to expect, and there is no output schema to cover that gap.

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 twenty-word sentence with no filler, and the subject ('One attachment') is front-loaded. It is a grammatical fragment rather than a clean sentence, but nothing is wasted.

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 two-parameter read tool with full schema coverage and no output schema, the description covers what the call returns but omits the scoping/preconditions (must the attachment belong to the given site?) and any failure behavior. It is adequate to attempt the call, not enough to call it confidently in edge cases.

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?

With 2 parameters at 100% schema description coverage, the schema already documents 'id' (attachment id) and 'site' (site id, see list_sites). The description adds nothing about the id/site pair or how the site scopes the lookup, 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 the resource ('One attachment') and enumerates the returned facets: optimization records, job history, and undo-for-replace status. That is far more specific than a restated name, though it is a noun phrase with no verb ('retrieve/get') and does not explicitly contrast itself with look-alike siblings such as media_get_backups or media_get_status.

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 explicit when-to-use statement and no named alternative. An agent must infer from the singular 'one attachment' that this is the single-item counterpart to list/bulk tools, and nothing tells it whether to reach for media_get_status or media_get_backups instead.

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