Skip to main content
Glama

Typebar (formerly SuperDocs)

list_jobs

Returns jobs sorted by most recent, optionally filtered by status. Use to monitor long-running AI edits started via chat_async, see which jobs are paused waiting for human approval, or audit completed work. Each job tracks the chat that started it, the changes made, and any HITL decisions logged.

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
limitNoMaximum number of jobs to return
statusNoFilter by job status
compactNoWhen true, omit each job's heavy result body + streamed intermediate events — returns just status/progress/ids/timestamps. Recommended for agents listing many jobs.

Output Schema

NameRequiredDescriptionDefault
jobsYesArray of job details.
totalYesTotal number of jobs returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses the ordering (most recent first), optional status filter, and what each job record contains (originating chat, changes, HITL decisions), which implies a read-only listing. It does not explicitly state that it is non-mutating, nor anything about default result size or pagination behavior beyond the schema's limit field.

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?

Three tight sentences: behavior first, then use cases, then what a job record contains. No filler, though the third sentence is the least essential given the output schema exists.

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 three-optional-param list tool with full schema coverage and an output schema, the description covers what it returns, how it's ordered, when to reach for it, and what a job tracks. The main remaining gap is sibling disambiguation from get_job/get_session_jobs.

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 100%, so limit, status, and compact are fully documented in structured fields, including the compact tradeoff. The description only restates the status filter and adds no syntax or semantics beyond the schema, which is the expected baseline when the schema does the work.

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 plus ordering and filtering behavior ("Returns jobs sorted by most recent, optionally filtered by status"). It's clear enough to separate from a single-job getter, but it never names the close siblings get_job or get_session_jobs, so the agent must infer the boundary from names alone.

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 three concrete use cases: monitoring long-running AI edits started via chat_async, spotting jobs paused for human approval, and auditing completed work. That is strong positive guidance, but there is no explicit when-not or alternative named (e.g. session-scoped listing via get_session_jobs).

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.