Skip to main content
Glama

List jobs

cron_list_jobs
Read-onlyIdempotent

Lists jobs with schedule, enabled/running state, next run, and last outcome in pages, so you can find a job's exact name or survey schedules.

Instructions

List jobs with schedule, enabled/running state, next run, and last outcome, one page at a time. Use it to find a job's exact name or to survey schedules. Each row has the same fields as cron_get_job, which fetches one job by name.

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": "cron_list_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMost jobs to return (default and maximum 200).
stateNoOnly jobs in this state. running means an instance is running now; scheduled means enabled and not running, including paused jobs.
filterNoCase-insensitive substring to match in job names.
offsetNoRows to skip. Pass the previous page's nextOffset to get the next page.

Output Schema

NameRequiredDescriptionDefault
jobsYes
pageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.2.73
    • addedInput schema / properties / filter / description
      Added value: +"Case-insensitive substring to match in job names."
    • addedInput schema / properties / limit / default
      Added value: +200
    • addedInput schema / properties / limit / description
      Added value: +"Most jobs to return (default and maximum 200)."
    • addedInput schema / properties / limit / maximum
      Added value: +200
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / offset / default
      Added value: +0
    • addedInput schema / properties / offset / description
      Added value: +"Rows to skip. Pass the previous page's nextOffset to get the next page."
    • addedInput schema / properties / offset / minimum
      Added value: +0
    • addedInput schema / properties / state / description
      Added value: +"Only jobs in this state. running means an instance is running now; scheduled means enabled and not running, including paused jobs."
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety profile is covered. The description adds real behavioral context beyond them: results come back paginated ("one page at a time") and each row is field-identical to cron_get_job, which tells the agent it can skip the detail call when it already has the row.

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?

Three short sentences: what it returns, when to use it, and how it relates to the sibling. No filler, and the return-field inventory is front-loaded before the usage hint.

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?

An output schema exists, so return values need no elaboration, and the four optional params are fully documented in-schema. For a read-only paginated list, nothing an agent needs in order to call it correctly is missing.

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%: limit, state, filter, and offset are each documented, including the state enum semantics and the nextOffset paging idiom. The description adds no parameter-level detail beyond implying name-based lookup; baseline 3 is appropriate when the schema carries the full burden.

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?

Specific verb + resource ("List jobs") plus the exact fields returned: schedule, enabled/running state, next run, last outcome. It also frames the resource against cron_get_job, so an agent can tell whether it is looking at a collection or a single record without opening the schema.

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?

"Use it to find a job's exact name or to survey schedules" gives two concrete selection contexts, and it names cron_get_job as the single-job alternative. It stops short of stating explicit exclusions (e.g., for run history see cron_list_runs), so the routing guidance is clear but not exhaustive.

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