Skip to main content
Glama

media_bulk_step

Runs one bulk media batch of up to 20 jobs now for sites without a working cron, staying within the one-step-per-2-seconds limit to prevent 429 errors.

Instructions

Run one bulk batch (up to 20 jobs) now, for sites without a working cron. The site allows one step per 2 seconds per user and answers 429 otherwise.

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

Input Schema

NameRequiredDescriptionDefault
siteYesSite id (see list_sites)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A4/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 disclose two non-obvious traits: a hard batch ceiling of 20 jobs and a throttling contract of one step per 2 seconds per user with a 429 response. That is genuinely useful operational context an agent cannot get from the schema. It leaves auth requirements, idempotency, and what the batch returns unstated.

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 sentences, no filler, and the execution scope is front-loaded ahead of the caveat and the rate limit. Every clause carries information an agent needs.

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 one-parameter action tool with no output schema, the definition covers the essentials: what runs, how large a batch may be, and the throttle it must respect. It could go further by saying whether the caller should re-invoke repeatedly to drain a queue, but nothing critical 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?

There is a single parameter, 'site', and schema coverage is 100%, with the schema itself pointing to list_sites. The description adds no further meaning about the site identifier, so the baseline of 3 applies. The '20 jobs' figure refers to batch size, not to any input field, so it does not deepen parameter semantics.

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 states a specific verb and resource: 'Run one bulk batch (up to 20 jobs) now'. The cap and the immediate-execution semantics make the operation concrete. It does not, however, distinguish this from nearby bulk siblings such as media_bulk_action or media_get_bulk, so an agent must infer the difference from the name alone.

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?

'for sites without a working cron' is an explicit use condition that implicitly excludes cron-driven sites, which is real routing guidance. It stops short of naming the alternative tool to use when cron is healthy, so a small inference remains.

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