Skip to main content
Glama

List jobs

list_jobs
Read-only

Lists your document jobs newest first with status and credits so you can find a job ID to check, cancel, or retry. Free.

Instructions

List this account's document jobs, newest first, with their status and credits - to find a job id for check_job, cancel_job or retry_job. Free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOnly jobs of this kind
limitNoHow many to return (default 20)
offsetNoHow many to skip, for the next page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.7.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description doesn't need to re-establish safety. It adds real context beyond that: results are ordered newest first, include status and credits, are scoped to this account, and cost no credits. It does not explain pagination continuation behavior, which is the remaining gap.

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?

A single dense sentence: purpose first, then ordering, return fields, the routing reason, and cost. Every clause earns its place with no filler or redundancy.

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 zero-required-parameter, read-only listing tool with a fully documented schema and no output schema, the description supplies the key missing pieces: what fields come back and what the results are for. Only the response envelope and pagination behavior remain unstated.

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 description coverage is 100%, so all three parameters (type, limit, offset) are already documented in the schema, establishing the baseline of 3. The description's 'newest first' remark weakly implies ordering semantics relevant to offset paging but adds no parameter-level detail such as default or maximum behavior.

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 this account's document jobs') plus scope, ordering ('newest first') and returned fields ('status and credits'). It also names the follow-up siblings (check_job, cancel_job, retry_job), so an agent can distinguish it from the project-oriented and mutating tools without opening any 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?

Gives an explicit use case: find a job id for check_job, cancel_job, or retry_job, which directly routes the agent to the right downstream tool. It also flags 'Free', useful for cost-sensitive decisions. No explicit when-not conditions are stated, but the practical guidance is strong.

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