Skip to main content
Glama

media_bulk_action

Control bulk media optimization by starting, pausing, resuming, canceling, or retrying jobs; retry re-queues failed attachments.

Instructions

Control bulk optimization: start (queues every attachment; type and include_restored apply only to start), pause, resume, cancel, or retry (re-queues the failed jobs).

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>",
      "action": "<action>"
    },
    "name": "media_bulk_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)
typeNostart only: optimize new files or reoptimize already optimized ones; default optimize
actionYesBulk action
include_restoredNostart only: also queue attachments that were restored on purpose

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.6/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 behavioral burden. It discloses the high-impact fact that start queues every attachment and that retry only touches failures, but says nothing about permissions, whether cancel reverts completed optimizations, whether pause persists across sessions, or what happens when start is called with an active job.

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 front-loaded sentence with zero filler; the action list leads and the qualifiers are attached inline. The nested parentheticals are slightly dense but still parse cleanly.

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 four-parameter mutation tool with no annotations and no output schema, the definition covers all valid actions and their parameter scoping. It leaves open the invocation context (existing job state, return value on start) but nothing an agent needs in order to choose an action 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 both optional parameters are already documented, including their 'start only' scoping. The description restates that scoping rather than adding new meaning, so the baseline 3 is appropriate.

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?

Names a specific resource (bulk optimization) and enumerates the five operations it controls: start, pause, resume, cancel, retry. The 'queues every attachment' phrasing distinguishes it from the per-attachment optimize tools in the catalog, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

Gives clear operational context for each action, including that retry re-queues only failed jobs and that type/include_restored apply only to start. It does not state preconditions (e.g. whether a job must already exist before pause/cancel) or exclusions versus the single-attachment tools.

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