Skip to main content
Glama

list_jobs

List the caller's standalone verification jobs (jobs that belong to a batch are excluded; read those with get_batch_results), newest first, paginated with limit (default 20, cap 96) and offset, optionally narrowed by status, verdict, a job_uuid prefix (search) and a creation range (from, to), and sorted by created_at or score with order. Use it to find a job_uuid or review recent single verifications; for bulk work use list_batches, and to read one job use get_verification. Requires the results:read scope.

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
toNoKeep only the jobs created at or before this RFC 3339 time.
fromNoKeep only the jobs created at or after this RFC 3339 time.
sortNoOrder by created_at (default) or score. A job without a score sorts as the smallest.
limitNoNumber of jobs to return (API default 20, cap 96).
orderNoOrder direction: desc (default) or asc.
offsetNoNumber of jobs to skip (default 0).
searchNoKeep only the jobs whose job_uuid starts with this text, ignoring case.
statusNoKeep only the jobs in one of these statuses: pending, queued, processing, completed, failed, canceled.
verdictNoKeep only the jobs whose result has one of these verdicts: valid, risky, invalid, unknown. Combined with status using AND.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / from
      Added value: +{
      +  "description": "Keep only the jobs created at or after this RFC 3339 time.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / order
      Added value: +{
      +  "description": "Order direction: desc (default) or asc.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / search
      Added value: +{
      +  "description": "Keep only the jobs whose job_uuid starts with this text, ignoring case.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / sort
      Added value: +{
      +  "description": "Order by created_at (default) or score. A job without a score sorts as the smallest.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / status
      Added value: +{
      +  "description": "Keep only the jobs in one of these statuses: pending, queued, processing, completed, failed, canceled.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / to
      Added value: +{
      +  "description": "Keep only the jobs created at or before this RFC 3339 time.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedInput schema / properties / verdict
      Added value: +{
      +  "description": "Keep only the jobs whose result has one of these verdicts: valid, risky, invalid, unknown. Combined with status using AND.",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full load, and it does well: it discloses the auth requirement (results:read scope), pagination defaults and the 96 cap, filter combination rules, and the exclusion of batch jobs. It stops short of describing the returned record fields or rate limits, which is the remaining gap for an unannotated read tool.

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?

One dense, front-loaded sentence with the resource and key constraint first, alternatives last. It is long but every clause carries information; slight density cost keeps it off a 5.

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?

With 9 optional params, no annotations and no output schema, the description covers scope, defaults, caps, filter semantics, routing to siblings and the required scope. Only the shape of returned job records is left unexplained, which is a modest gap for a read-only list tool.

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 every parameter (limit, offset, sort, order, status, verdict, search, from, to) is already documented in the schema. The description adds a readable summary of the filter set and sort keys but no format or syntax detail beyond what the schema provides; baseline 3 applies.

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 the exact resource (the caller's standalone verification jobs), its scope boundary (batch jobs excluded), and ordering (newest first), which is enough to separate it from list_batches and get_batch_results without opening a schema.

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?

Gives explicit use cases (find a job_uuid, review recent single verifications) and names the alternatives with the condition that selects them: get_batch_results for batched jobs, list_batches for bulk work, get_verification for a single job by id.

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