Skip to main content
Glama

media_get_backups

Summarizes media backups for a WordPress site, showing original file count, total bytes, oldest backup, and backup directory status without returning the path.

Instructions

Backup summary of originals: count, bytes, oldest backup and whether a backup directory is configured. Never returns the path.

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_backups"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.6/5.0
Behavior4/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, and it does disclose a genuinely useful behavioral trait: it never returns the path, which stops an agent from expecting filesystem paths. It also enumerates the returned fields, making the response shape predictable without an output schema. It stops short of stating auth or permission requirements, but for a side-effect-free read that is a minor gap.

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?

Two tight sentences, front-loaded with the resource and its scope, followed immediately by the most decision-relevant caveat. Nothing is redundant or padded.

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

Completeness4/5

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

With one simple parameter, no annotations, and no output schema, the description does the necessary work by listing the returned fields and the notable omission (no path). A brief indication of what a zero-count or unconfigured-directory result means would make it fully complete, but nothing essential for calling it correctly is missing.

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?

The single 'site' parameter is fully documented in the schema ('Site id (see list_sites)'), so schema description coverage is 100% and the baseline of 3 applies. The description adds no additional meaning about the parameter — no format, default, or scoping notes beyond what the schema already says.

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 gives a specific verb+resource ('Backup summary of originals') and enumerates exactly what is summarized: count, bytes, oldest backup, and whether a backup directory is configured. It is clearly a read-only inspection call, distinguishable in spirit from media_cleanup_backups, but it does not name or explicitly contrast with any sibling.

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 when-to-use guidance at all — nothing says this is a pre-flight check before media_cleanup_backups, nor when to prefer it over media_get_stats or media_get_settings. The usage is only inferable from the tool name and the word 'summary'.

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