Skip to main content
Glama

media_cleanup_backups

Permanently delete backups of original media files by age, attachment ID, or all at once. Frees storage, but cleaned images can no longer be restored.

Instructions

Delete backups of originals. DESTRUCTIVE: originals of cleaned images can no longer be restored. Needs exactly one scope: older_than_days (backups older than N days), ids (attachment ids, at most 500) or all: true (every backup). Returns { deleted, bytes, remaining, skipped }.

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

Input Schema

NameRequiredDescriptionDefault
allNoScope: true deletes every backup
idsNoScope: attachment ids whose backups to delete, at most 500
siteYesSite id (see list_sites)
older_than_daysNoScope: delete backups older than this many days, 0..3650

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does real work: it labels the operation DESTRUCTIVE, explains the irreversible consequence (originals of cleaned images can no longer be restored), and states a hard mutual-exclusivity rule that the schema does not encode. It omits permission/auth requirements and any rate or timing behavior, which keeps it short of a 5.

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?

Four tight sentences, front-loaded with the action and then the destruction warning before the scoping rules. The return-shape sentence earns its place because no output schema exists.

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?

For a destructive, un-annotated mutation with no output schema, the description covers the critical pieces: irreversibility, scope exclusivity, the ids cap, and the returned fields. It could still mention permission requirements or how to obtain valid attachment ids, but nothing essential for a safe call 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?

Schema coverage is 100%, so baseline is 3, and the description largely restates the per-parameter meaning (older_than_days, ids, all) already documented in the schema. Its one genuine addition is the constraint that exactly one of these scopes must be used, which the JSON schema does not enforce.

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?

States a specific verb and resource ("Delete backups of originals") and clarifies the affected object as backups rather than originals, which separates it from the read-only media_get_backups. It never names a sibling explicitly, so an agent must still infer the boundary with media_eio_cleanup or media_bulk_restore on its own.

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 description says a scope is required and implies caution via "DESTRUCTIVE", which gives some directional guidance for invoking it. It does not say when this tool is preferable to media_eio_cleanup, whether a dry run or media_get_backups inspection should come first, or what prerequisites (permissions, existing backups) apply.

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