Skip to main content
Glama

media_get_bulk

Get bulk media optimization status to see if jobs are running, paused, or idle, plus counts of done, pending, and failed items.

Instructions

Bulk optimization state: running, paused or idle, with counts of done, pending and 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>"
    },
    "name": "media_get_bulk"
  }
}

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 disclosure burden; it partially meets this by describing the payload (state plus done/pending/failed counts), which implies a non-mutating status read. It omits any statement about permissions, whether the call errors or returns idle when no job exists, and whether the counts are cumulative or per-run.

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?

One compact sentence with no filler, and the resource is front-loaded before the returned fields. It is a fragment rather than a full clause, which is efficient but slightly less clear than an explicit verb would be.

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?

With one parameter and no output schema, the description should fully define the return shape, and it does name the state values and count buckets. It still leaves open what happens when no bulk job has ever run for the given site, which is the main ambiguity for a status tool.

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 description coverage is 100% and the single 'site' parameter is documented in-schema with a pointer to list_sites. The description adds nothing about how site scopes the reported state, 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 identifies a specific resource — bulk optimization state — and enumerates the returned values (running/paused/idle plus done/pending/failed counts), so an agent can tell this is a status read rather than a bulk mutation. It does not, however, explicitly contrast itself with lookalike siblings such as media_get_status or media_bulk_step, leaving the agent to infer the boundary from names alone.

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 to call this before or after media_bulk_action, nor how it differs from media_get_status. The agent must guess the call context from the phrase 'Bulk optimization state' by itself.

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