Skip to main content
Glama

media_get_stats

Retrieve media library statistics for a WordPress site, including attachments by state, bytes saved, and backup summary.

Instructions

Library statistics: attachments by state, bytes saved, and the backup summary.

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it does disclose the shape of the returned data (state breakdown, bytes saved, backup summary), which is the most useful behavioral fact for a reporting tool. It says nothing about read-only semantics, cost/aggregation over large libraries, or authorization requirements.

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?

A single short sentence with the key output categories front-loaded and no filler. It is a noun-phrase fragment rather than a complete statement, which slightly reduces clarity about the action being performed.

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?

For a one-parameter, read-only stats tool this is minimally adequate: the description is the only source of return-value information since no output schema exists, and it covers that at a high level only. Differentiation from the near-duplicate mcp_get_media_stats is the notable omission.

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?

Only one parameter exists and schema description coverage is 100%, with 'Site id (see list_sites)' already documenting it. The description adds no meaning beyond that, so the baseline 3 applies.

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 the resource ('Library statistics') and enumerates the three result categories — attachments by state, bytes saved, backup summary — so an agent knows this is an aggregated reporting tool rather than a per-item fetch. It lacks an explicit verb and does not distinguish itself from the similarly named sibling mcp_get_media_stats.

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 call this versus siblings such as mcp_get_media_stats, media_get_status, or media_get_backups, nor any precondition beyond the required site id. The agent must infer the use case purely from the noun 'statistics'.

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