Skip to main content
Glama

List recent batches

list_batches
Read-onlyIdempotent

The account’s batches of one scene from the last 24 hours, newest first, with each picture’s progress — and how many pictures its plan lets one batch hold (allowance; 0 means the plan includes no batches).

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": {
      "scene": "<scene>"
    },
    "name": "list_batches"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
sceneYes

Output Schema

NameRequiredDescriptionDefault
batchesYes
allowanceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed6 schema fields changed
    • removedOutput schema / properties / batches / items / properties / items / items / properties / error_code / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / batches / items / properties / items / items / properties / error_code / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / batches / items / properties / items / items / properties / job_id / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / batches / items / properties / items / items / properties / job_id / type
      Added value: +[
      +  "string",
      +  "null"
      +]
    • removedOutput schema / properties / batches / items / properties / settled_at / anyOf
      Removed value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • addedOutput schema / properties / batches / items / properties / settled_at / type
      Added value: +[
      +  "string",
      +  "null"
      +]
  3. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description still adds real behavioral context beyond them: a fixed 24-hour lookback, newest-first ordering, per-picture progress in each result, and the allowance field including the edge case that 0 means the plan includes no batches.

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?

A single sentence with no filler, and the primary scoping information (account, scene, last 24 hours, newest first) is front-loaded. The trailing parenthetical on allowance is slightly dense but earns its place by defining a return field and its zero case.

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 a rich annotation set and an output schema, the definition is close to complete; the description's explanation of return fields is a bonus. The gap is the unexplained limit parameter and the absence of any note about maximum result size (10), which an agent needs to reason about truncation.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry parameter meaning. It partially covers 'scene' by saying batches belong to one scene, but the 'limit' parameter (integer 1-10) is never mentioned, so an agent gets no guidance on what it caps or what the default is.

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 specifies the resource (batches), the scope (one scene, last 24 hours), and the ordering (newest first), which is enough for an agent to distinguish it from the singular get_batch and from start_batch. It never states the verb 'list' outright, but 'The account's batches ... newest first' conveys a listing unambiguously.

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?

The 24-hour window and single-scene constraint imply when this tool applies, but the description gives no explicit when-to-use or when-not guidance and does not point to siblings such as get_batch for a single batch or retry_batch/start_batch for mutations. Usage is inferable rather than stated.

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.

Resources