Skip to main content
Glama

list_jobs

Read-onlyIdempotent

Retrieve tracked jobs with their tracking fields, newest first, and filter by status to review all postings in a specific stage, including closed roles.

Instructions

Tracked jobs with their tracking fields, newest first, including closed postings. A plain list by status (e.g. every skipped job); for ranked new jobs use get_digest, for the next to apply to list_queued_jobs, and for follow-ups list_applications.

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
statusNoOnly jobs with this status; omit for all.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.10.0
    • changedInput schema / properties / status / anyOf
      Previous value: -[
      -  {
      -    "enum": [
      -      "new",
      -      "shown",
      -      "queued",
      -      "applied",
      -      "screening",
      -      "interviewing",
      -      "offer",
      -      "rejected",
      -      "withdrawn",
      -      "skipped"
      -    ],
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "new",
      +      "shown",
      +      "queued",
      +      "applied",
      +      "screening",
      +      "interviewing",
      +      "offer",
      +      "rejected",
      +      "withdrawn",
      +      "skipped",
      +      "snoozed"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
  2. Changed2 schema fields changedv0.2.3
    • changedInput schema / properties / status / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]New value: +[
      +  {
      +    "enum": [
      +      "new",
      +      "shown",
      +      "queued",
      +      "applied",
      +      "screening",
      +      "interviewing",
      +      "offer",
      +      "rejected",
      +      "withdrawn",
      +      "skipped"
      +    ],
      +    "type": "string"
      +  },
      +  {
      +    "type": "null"
      +  }
      +]
    • addedInput schema / properties / status / description
      Added value: +"Only jobs with this status; omit for all."
  3. First observedv0.1.0

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds useful ordering ('newest first') and the non-obvious inclusion of closed postings, but says nothing about result volume, pagination, or whether all tracked jobs are returned unbounded.

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 sentences, front-loaded with what the tool returns, followed by a compact routing clause. Every phrase carries signal; there is no restatement of the tool name or filler.

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?

An output schema exists, so return values need no explanation, and one optional filter parameter is fully documented. The only gap is the absence of any statement about result size or pagination for what could be a large job list.

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 100% and the single parameter is documented there, so baseline would be 3. The description earns an extra point by illustrating filter semantics with a concrete case ('every skipped job'), which clarifies intent beyond the enum description alone.

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 ('Tracked jobs with their tracking fields') plus ordering ('newest first') and scope ('including closed postings'). An agent can distinguish it from get_digest, list_queued_jobs, and list_applications 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?

Explicitly names when to use this tool ('a plain list by status, e.g. every skipped job') and routes to three alternatives with the condition that selects each: get_digest for ranked new jobs, list_queued_jobs for the next to apply to, list_applications for follow-ups. Nothing is left to inference.

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