Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_list_media

Retrieve WordPress media library items, applying optional search filters and pagination controls to locate specific files.

Instructions

List WordPress media library items

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "wp_list_media"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
searchNo
per_pageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

The description does not mention any behavioral traits such as pagination, ordering, or response format. No annotations are provided to fill gaps. The tool may return a list of media items, but details like maximum results, caching, or error behavior are missing.

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?

The description is a single, concise sentence with no wasted words. It is front-loaded with the action and resource. However, it could be slightly longer to include critical details without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description is severely incomplete given no annotations, no output schema, and three parameters with no documented meaning. The tool likely returns a list of media objects, but return structure, pagination metadata, and default behavior are entirely omitted. A tool with this complexity requires more explanation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds no meaning to any of the 3 parameters (per_page, page, search). With schema description coverage at 0%, the description fails to compensate. The schema itself provides basic names and types, but users must infer usage from the schema alone. The description does not explain that 'search' filters by title or that 'per_page' and 'page' enable pagination.

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 clearly states the verb 'List' and the resource 'WordPress media library items'. It is specific enough to distinguish from sibling tools like 'wp_get_media' which retrieves a single item. However, it could be more precise (e.g., 'list all media items with pagination and search').

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?

No guidance on when to use this tool versus alternatives like 'wp_get_media' or when not to use it. The description lacks context about typical use cases or prerequisites. Sibling tools exist for getting, uploading, updating, and deleting media, but no differentiation is provided.

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