Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: List media

wordpress_list_media
Read-only

List WordPress media library items by type with pagination; returns image, video, and document URLs plus metadata.

Instructions

[UNIFIED] List media library items. Returns images, videos, documents with URLs and metadata.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
siteYes
per_pageNo
media_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful context by saying the results include URLs and metadata for images, videos, and documents. It stops short of disclosing pagination behavior, default ordering, total-count semantics, or how media_type filters results — gaps that matter for a paged list tool.

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?

Two short, front-loaded sentences with no filler. The '[UNIFIED]' tag is the only wasted token, but it does not obscure the meaning.

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

Completeness2/5

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

With no output schema, four undocumented parameters, and no annotations beyond readOnlyHint, the description carries most of the burden and falls well short — it says nothing about pagination, filtering values, or response shape beyond a one-clause list of media kinds. An agent could call it, but would likely mis-set per_page/media_type defaults.

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

Parameters2/5

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

Schema description coverage is 0%, so the schema names four parameters without explaining any of them. The description mentions image/video/document types, which weakly hints at the media_type filter, but never explains page, per_page, media_type, or site semantics, leaving the agent to guess accepted values and defaults.

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 a specific verb and resource ('List media library items') and enumerates the returned item types (images, videos, documents), so an agent knows exactly what operation this performs. It does not, however, distinguish itself from the singular wordpress_get_media or from other list_* siblings; the '[UNIFIED]' prefix is unexplained jargon that adds no clarity.

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 statement of when to use this tool versus wordpress_get_media (single item) or any other sibling, and no guidance on pagination or result limits. The agent must infer usage from the name alone.

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