Skip to main content
Glama
cvrt-jh

wordpress-mcp

by cvrt-jh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

mcp_list_media

List WordPress media library items with filters for site, search, MIME type, pagination, and sort order to find and manage images, video, audio, or files.

Instructions

List media library items with filtering

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number
siteYesSite id (see list_sites)
orderNoSort directionDESC
searchNoSearch term
orderbyNoOrder by fielddate
per_pageNoItems per page
mime_typeNoFilter by MIME type (image, video, audio, application)

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+]
  2. First observedv2.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral-disclosure burden. 'List' implies a read operation, but the description does not state permissions, pagination behavior, rate limits, or return characteristics, leaving important behavior unaddressed.

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?

The description is a single, front-loaded phrase with no wasted words. It is appropriately sized for the amount of information it chooses to convey.

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?

The schema is rich and fully described, covering required and optional parameters and defaults. However, with no annotations and no output schema, the description is minimally complete: it omits when-to-use routing and behavioral details that would help an agent invoke it confidently.

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?

The input schema has 100% description coverage, so the schema already documents all seven parameters in detail. The description adds only the general phrase 'with filtering' and does not enrich parameter meaning beyond the schema.

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: 'List media library items with filtering.' It is clear what the tool does, but it does not distinguish this tool from sibling listers such as wp_list_media or mcp_get_media.

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?

The description gives no explicit guidance about when to use this tool versus alternatives. There is no mention of when not to use it, prerequisites, or how it differs from wp_list_media or mcp_get_media.

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