Skip to main content
Glama

list_jobs

Read-only

List background jobs newest first with status and progress; completed jobs stay available for one hour.

Instructions

List your background jobs (newest first) with their status and progress. Finished jobs are kept for an hour.

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
limitNoMax jobs to return (default 20)
statusNoOnly jobs with this status

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.0.1

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the description's job is to add context — and it does: newest-first ordering, that status and progress are included, and the one-hour retention window for finished jobs. Retention in particular is non-obvious behavior an agent needs. It omits whether listing itself prunes or affects jobs, but the read-only hint covers the safety question.

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?

Two short sentences with no filler. Ordering and return content come first, and the retention caveat follows as the second, equally load-bearing sentence.

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 two-optional-parameter read-only list tool with no output schema and fully covered parameter descriptions, the definition is nearly sufficient. A brief note on what happens with very large job sets, or how this differs from the scheduled/PA job listers, is the only meaningful omission.

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%, with both optional parameters (limit default 20, status enum) fully documented in the schema. The description adds nothing about filtering or result capping, so baseline 3 is appropriate.

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 gives a specific verb and resource ('List your background jobs') plus scope ('your'), ordering ('newest first'), and returned fields ('status and progress'). It does not distinguish itself from siblings such as list_pa_jobs or list_scheduled_jobs, which an agent could easily confuse with this one.

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

Usage Guidelines2/5

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

There is no explicit guidance on when to call this versus the other job-listing tools. The possessive 'your' hints at a personal scope, but no condition or alternative is stated, leaving the agent to infer selection from names alone.

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

Deploy Server

Other Tools