AutoWP MCP Server

search-media

Search WordPress media by title, caption, or filename, and filter results by media type or date to locate the right image, video, or audio.

Instructions

Search WordPress media library by keyword, type, or date

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": {
      "query": "<query>"
    },
    "name": "search-media"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum results to return
`query`	Yes	Search query for title, caption, or filename
`dateAfter`	No	Find media after this date (ISO format)
`mediaType`	No	Filter by media type	any
`dateBefore`	No	Find media before this date (ISO format)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 31, 2026

TDQS

B3.4/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 burden. It states only the search action and does not disclose whether the operation is read-only, what the return format is, or if there is any pagination or default behavior. This is minimal disclosure beyond the bare function.

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, focused sentence that immediately conveys the tool's purpose. There is no redundant or filler content, and it is well front-loaded with the main verb.

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 and no annotations, the description should cover return values, defaults, and behavioral constraints. It only states the search capabilities, omitting what results look like, the default limit, and any rate-limit or auth considerations. This is incomplete for a moderately configured search tool.

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 coverage is 100%, so the schema already describes all parameters. The description's mention of 'keyword, type, or date' maps to query, mediaType, and dateBefore/dateAfter but adds no new semantic details beyond what the schema provides. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Search'), the resource ('WordPress media library'), and the filtering criteria ('by keyword, type, or date'). This is specific and distinguishes it from sibling tools like list-media or get-media-details.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The usage is implied by the purpose—use this to search media—but there is no explicit when-to-use, when-not-to-use, or mention of alternatives like list-media for unfiltered listing. The description lacks exclusion guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.