Skip to main content
Glama

wordpress_get_unused_media

wordpress_get_unused_media

Scan your WordPress media library to identify files not attached to any posts or pages, enabling efficient cleanup and improved storage management.

Instructions

Find unused media files in library

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.0
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
  2. First observed

TDQS

B3.3/5.0
Behavior2/5

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

With no annotations to fall back on, the description carries full responsibility for behavioral disclosure. 'Find' implies a read-only operation, but the description does not state what it returns, how 'unused' is determined, or any limitations. This lack of detail leaves significant behavioral aspects undisclosed for a tool with no annotations.

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 extremely concise, consisting of a single sentence with no fluff. Every word earns its place. However, it is almost too terse, lacking any structure or additional useful clauses, so it does not fully earn a 5.

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?

For a tool with no parameters, no annotations, and no output schema, the description is not complete enough. It does not explain what constitutes 'unused' media, what format the results take, or any edge cases. Users would need additional information to use this tool effectively.

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

Parameters4/5

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

The tool has no parameters, so the baseline score is 4. The description does not need to explain parameter semantics, and none are present. It correctly does not add irrelevant parameter information.

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 'Find unused media files in library' clearly identifies the action (find) and resource (unused media files in the library). It distinguishes itself from sibling tools like wordpress_get_media by specifying 'unused', which clarifies the unique purpose of this tool.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any specific use case, prerequisites, or exclusions. The only context is implicit from the name and description, which is not sufficient for clear decision-making.

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