Skip to main content
Glama

media_list_attachments

Lists image attachments newest first with their optimization records, optionally filtered by status for a WordPress site.

Instructions

List image attachments, newest first, with their optimization records, optionally filtered by status.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage, default 1
siteYesSite id (see list_sites)
statusNoOnly attachments in this state
per_pageNoPer page, 1..100, default 20

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does add useful behavior beyond the name: return ordering (newest first) and that each row carries optimization records. It omits permissions/auth requirements, whether results are paginated in practice, and total-count or empty-result behavior, which leaves meaningful gaps for a zero-annotation tool.

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?

A single sentence with the resource and ordering front-loaded and no filler. Every clause (subject, sort order, payload, filter) carries distinct information.

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 simple paginated read tool with fully described parameters and no annotations, the description covers what is returned and in what order, which compensates for the missing output schema. It could be stronger by noting pagination behavior or that it is a read-only, non-mutating call.

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%, including a status enum and page/per_page bounds, so the parameters are already fully documented by structured data. The description only restates the optional status filter and adds the default sort order, which is minor added meaning.

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 gives a specific verb and resource ("List image attachments") plus two distinguishing traits: ordering ("newest first") and payload ("with their optimization records"). It does not explicitly contrast with near-name siblings such as mcp_list_media or media_get_attachment, so differentiation is implied by the optimization-record payload rather than stated.

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, when-not-to-use, or named alternative guidance. The scope phrase "image attachments ... with their optimization records" hints at the tool's niche, and "optionally filtered by status" hints at a filter workflow, but an agent must infer when to pick this over mcp_list_media or media_get_attachment.

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