Process the next item in a queued background job to prevent API flooding during media stack operations.
Processes a single sequential block item from an active background batch queue entry to prevent API flooding. (Jobs that have been started are also advanced automatically, one item per minute, by the job runner.)
| Name | Required | Description | Default |
|---|---|---|---|
| jobId | Yes | The unique tracking ID of the active job array to step execute. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the disclosure burden. It usefully discloses that exactly one sequential block item is processed, that the job must be active, and that auto-advance already occurs. But it does not mention side effects on job state, error conditions, reversibility, or what happens when no steps remain.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two sentences with no filler. The first sentence front-loads the action and purpose; the second adds relevant automatic-advancement context. Appropriately sized for a single-parameter tool.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
This is a simple one-parameter tool, but with no annotations and no output schema, the description must do more. It explains what and why, but omits return/outcome details and side-effect behavior, leaving the agent with only partial context for a mutating action.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema already fully describes jobId as the unique tracking ID of the active job array, so the baseline is 3. The description adds some contextual language around 'active' and 'block item' but does not materially extend the parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States precise behavior: processes a single sequential block item from an active background batch queue entry, with a clear rationale (prevent API flooding). This is specific enough to distinguish it from sibling read/manage tools like get_background_jobs and update_job_status, even without naming them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied rather than explicit: the description suggests manual stepping exists to prevent API flooding, and notes that started jobs also auto-advance one item per minute. However, it does not state when not to use this tool or name an alternative explicitly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.