Skip to main content
Glama

mcp_list_media

List WordPress media library items with IDs, titles, URLs, MIME types, dates, image details, and paging totals; filter by MIME type, search terms, page, and sort order.

Instructions

List media library items (id, title, url, mime_type, date; images also alt, width, height) with paging totals

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": "mcp_list_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default 1)
siteYesSite id (see list_sites)
orderNoSort direction (default DESC)
searchNoSearch term
orderbyNoOrder by field (default date)
per_pageNoItems per page (default 20)
mime_typeNoFilter by MIME type or top-level type (image, video, audio, application, image/png)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv3.14.0
    • changedInput schema / properties / mime_type / description
      Previous value: -"Filter by MIME type (image, video, audio, application)"New value: +"Filter by MIME type or top-level type (image, video, audio, application, image/png)"
    • removedInput schema / properties / order / default
      Removed value: -"DESC"
    • changedInput schema / properties / order / description
      Previous value: -"Sort direction"New value: +"Sort direction (default DESC)"
    • removedInput schema / properties / orderby / default
      Removed value: -"date"
    • changedInput schema / properties / orderby / description
      Previous value: -"Order by field"New value: +"Order by field (default date)"
    • addedInput schema / properties / orderby / enum
      Added value: +[
      +  "date",
      +  "modified",
      +  "title",
      +  "name",
      +  "author",
      +  "parent",
      +  "menu_order",
      +  "rand",
      +  "none"
      +]
    • removedInput schema / properties / page / default
      Removed value: -1
    • changedInput schema / properties / page / description
      Previous value: -"Page number"New value: +"Page number (default 1)"
    • addedInput schema / properties / page / minimum
      Added value: +1
    • changedInput schema / properties / page / type
      Previous value: -"number"New value: +"integer"
    • removedInput schema / properties / per_page / default
      Removed value: -20
    • changedInput schema / properties / per_page / description
      Previous value: -"Items per page"New value: +"Items per page (default 20)"
    • addedInput schema / properties / per_page / minimum
      Added value: +1
    • changedInput schema / properties / per_page / type
      Previous value: -"number"New value: +"integer"
  2. Changed2 schema fields changedv3.4.0
    • addedInput schema / properties / site
      Added value: +{
      +  "description": "Site id (see list_sites)",
      +  "type": "string"
      +}
    • addedInput schema / required
      Added value: +[
      +  "site"
      +]
  3. First observedv2.0.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations exist, so the description carries the full load: it discloses the returned field set (including image-only fields) and that paging totals are included, which is meaningful behavioral context. However, it says nothing about permission requirements, how totals relate to filters, or pagination edge cases, so gaps remain for a read tool with seven parameters.

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?

One tightly packed sentence that front-loads the verb and resource, then the returned fields. The parenthetical field list is dense but each item earns its place; nothing is redundant.

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?

With no output schema, describing the return fields is a useful compensation, and the schema fully documents the seven inputs. Still, for a filtered, paginated list tool, the definition omits how filters and paging totals interact and offers no navigation guidance, leaving it adequate rather than complete.

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% and every parameter carries an inline description with defaults and enum values, so the schema already does the heavy lifting. The description adds no filter syntax or interaction detail beyond noting paging totals, which is the baseline 3 case.

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 opens with a specific verb and resource ('List media library items') and enumerates the returned fields, so the agent knows exactly what this tool yields. It stops short of differentiating itself from sibling listers such as wp_list_media or media_list_attachments, which keeps it below 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 explicit when-to-use or when-not-to-use guidance and no named alternative. Use for browsing the media library is only implied by the verb 'List', leaving the agent to infer selection among several media-listing siblings.

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