Skip to main content
Glama

Get batch items

get_batch_items
Read-onlyIdempotent

Page through a batch's results by its taskId (cursor, limit up to 50). fields keeps only the named item fields (plus id, url, status, createdAt), e.g. ["json"] for a JSON batch. With maxResults the tool follows the cursors itself and answers { items, nextCursor, hasMore, stoppedBy }.

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

Input Schema

NameRequiredDescriptionDefault
idYes
debugNo
limitNo
cursorNo
fieldsNo
maxResultsNoFollow the cursors and return up to this many items in all.

Output Schema

NameRequiredDescriptionDefault
itemsYes
hasMoreNo
stoppedByNosize: the answer reached its size budget; read on from nextCursor.
nextCursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / fields
      Added value: +{
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • changedInput schema / properties / maxResults / description
      Previous value: -"Follow cursors from cursor on and return up to this many items in all (pages of at most 50); the answer is then { items, nextCursor, hasMore, stoppedBy }."New value: +"Follow the cursors and return up to this many items in all."
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world behavior, so the description's job is to add operational detail. It does: it discloses pagination semantics, that maxResults makes the tool follow cursors internally, and that a stoppedBy marker reports why iteration ended — real behavior beyond the annotations.

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?

Two dense sentences that front-load the core paging behavior, then add projection and auto-follow detail. No filler, though the parenthetical about fields is packed tightly enough to slow a quick read.

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?

Covers the complex parts — projection fields, limits, and cursor-following output shape — which is enough for a six-parameter paging tool with an output schema already describing returns. The undocumented debug flag is a minor gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 17%, so the description has to carry the parameter burden. It explains id as a taskId, documents limit's cap of 50 and cursor's paging role, clarifies fields as a projection that always retains id/url/status/createdAt, and gives an example. Only debug remains undocumented.

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?

States a specific verb and resource: "Page through a batch's results by its taskId." That clearly separates it from get_batch (batch metadata) and get_batch_errors (failures), although it never names those siblings.

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

Usage Guidelines3/5

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

Implies the tool is for paging through result items and explains how cursor/limit versus maxResults differ in effort, but gives no explicit rule for when to use this instead of get_batch or get_batch_errors.

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.