Skip to main content
Glama

List recent jobs

list_recent_jobs
Read-only

Most recent generation jobs in one project, newest first (limit 1-200), with status, outputs and credits. The project is project if given, else the API key's default; jobs in other projects are not included, so to see everything call list_projects and pass each. Filter by workflow_run_id to see the steps of one workflow run.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
projectNo
workflow_run_idNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations give readOnlyHint=true and openWorldHint=true, so safety is covered; the description adds the important scoping behavior (project fallback to API key default) and the newest-first ordering plus limit range. It doesn't mention pagination beyond the limit or what happens when limit exceeds available jobs, which keeps it just short of 5.

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?

Front-loaded with the resource and ordering, then scope caveat, then filter guidance. Three sentences with little waste, though the cross-project workaround sentence is slightly dense and the limit-range parenthetical is tucked mid-sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists, so return values need not be spelled out, yet the description names status, outputs and credits. Combined with the project-scoping explanation and filter semantics, an agent has everything needed to call and interpret this correctly.

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 0%, so the description carries the burden and does explain all three: limit (1-200) though the schema default is 20 which is not clarified, project (fallback to API key default), and workflow_run_id (filters to steps of one run). This is meaningfully more than the bare schema titles provide.

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 ('Most recent generation jobs in one project'), specifies ordering (newest first) and the fields returned (status, outputs, credits). It also distinguishes itself from get_job and list_runs by scoping to a project and a recency list.

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

Usage Guidelines5/5

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

Explicitly states the project defaulting rule and the exclusion ('jobs in other projects are not included'), then names the alternative pattern: call list_projects and pass each. It also gives a concrete condition for using workflow_run_id to see one run's steps.

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