Skip to main content
Glama

Get batch errors

get_batch_errors
Read-onlyIdempotent

List a batch's items that did not succeed (status failed, blocked, cancelled or budget_exceeded), each as get_batch_items lists it: { items, nextCursor, hasMore }, in pages of up to 100 (cursor, limit). A URL robots.txt refused is among them, blocked with its blockReason. notServed lists pages read but not the one asked for.

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": {
      "id": "<id>"
    },
    "name": "get_batch_errors"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
debugNoKeep each item's usage and trace. Default false.
limitNo
cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / debug
      Added value: +{
      +  "description": "Keep each item's usage and trace. Default false.",
      +  "type": "boolean"
      +}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's job is to add operational context, which it does: page size cap, the returned envelope { items, nextCursor, hasMore }, and the fact that robots.txt-refused URLs appear as blocked with a blockReason. The trailing notServed sentence is murkier and reads like it belongs to a crawl-pages tool, adding some ambiguity rather than clarity.

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?

Single dense paragraph, front-loaded with the filter definition and followed by return shape and paging. Nearly every clause carries information, though the final notServed sentence is cryptic and could be cut or clarified without loss to the core task.

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?

With no output schema, the description correctly supplies the return envelope and status vocabulary, and annotations handle the safety profile. The main residual gap is identifying what `id` refers to and the meaning of notServed in this tool's context.

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 only 25% (only debug is documented), so the description must compensate. It does partially — cursor and limit are tied to paging of up to 100 — but the limit ceiling is already in the schema's maximum, and the required `id` parameter is never explained (batch id from batch_scrape?). Debug is left entirely to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("List a batch's items that did not succeed") and enumerates the exact statuses in scope (failed, blocked, cancelled, budget_exceeded). The phrase "each as get_batch_items lists it" explicitly positions it against the sibling that returns all items, so an agent can distinguish the two without opening either schema.

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?

The filtering condition is clear: use this when you only want the non-successful items, and the reference to get_batch_items implies where to go for the full list. It stops short of an explicit "use get_batch_items instead when..." exclusion, but the selection context is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.