Skip to main content
Glama
musharna

jobd

by musharna
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

jobd_list

List jobs on the broker with per-state counts. Defaults to the active set (queued/assigned/running); filter by state (e.g. ['failed']), project, or a finished_at window (finished_after/finished_before) to find past runs.

Instructions

List jobs on the broker with per-state counts. Defaults to the active set (queued/assigned/running); filter by state (e.g. ['failed']), project, or a finished_at window (finished_after/finished_before) to find past runs. Each row is a compact summary: job_id, project, state, host, exit_code, queued_at, started_at, finished_at, duration_s — call jobd_status for a job's full record. Use to answer 'what is running / queued right now?', 'what failed overnight?', or to locate a job id you've lost.

Input Schema

NameRequiredDescriptionDefault
limitNoMax jobs returned (newest first; clamped to [1,200]). `counts` still covers every job matching the filters; a `truncated` field reports how many were cut.
stateNoStates to include — any of: queued, assigned, running, completed, failed, cancelled, preempted, orphaned, scheduling_timeout. Omit for the active set (queued/assigned/running); pass [] for all states.
projectNoRestrict to one project's jobs (the --project value used at submit).
finished_afterNoOnly jobs with finished_at at or after this: ISO-8601 (no offset = UTC) or relative (2h, 3d, 1w = that long ago). With a window and no state, every terminal state is included and counts cover the window exactly.
finished_beforeNoOnly jobs with finished_at before this (exclusive); same formats as finished_after.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.52
    • addedInput schema / properties / finished_after
      Added value: +{
+  "description": "Only jobs with finished_at at or after this: ISO-8601 (no offset = UTC) or relative (2h, 3d, 1w = that long ago). With a window and no state, every terminal state is included and counts cover the window exactly.",
+  "type": "string"
+}
    • addedInput schema / properties / finished_before
      Added value: +{
+  "description": "Only jobs with finished_at before this (exclusive); same formats as finished_after.",
+  "type": "string"
+}
  2. Changed2 schema fields changedv0.5.47
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / state / items / enum
      Added value: +[
+  "queued",
+  "assigned",
+  "running",
+  "completed",
+  "failed",
+  "cancelled",
+  "preempted",
+  "orphaned",
+  "scheduling_timeout"
+]
  3. Addedv0.5.36
  4. Removedv0.5.35
  5. Changed2 schema fields changedv0.5.12
    • changedInput schema / properties / limit / description
      Previous value: -"Advisory cap on returned jobs (the broker currently returns its default window)."New value: +"Max jobs returned (newest first; clamped to [1,200]). `counts` still covers every job matching the filters; a `truncated` field reports how many were cut."
    • changedInput schema / properties / state / description
      Previous value: -"States to include — any of: queued, assigned, running, completed, failed, cancelled, preempted, orphaned, scheduling_timeout. Currently only the first is forwarded to the broker (single state_filter)."New value: +"States to include — any of: queued, assigned, running, completed, failed, cancelled, preempted, orphaned, scheduling_timeout. Omit for the active set (queued/assigned/running); pass [] for all states."
  6. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Advisory cap on returned jobs (the broker currently returns its default window)."
    • addedInput schema / properties / project / description
      Added value: +"Restrict to one project's jobs (the --project value used at submit)."
    • changedInput schema / properties / state / description
      Previous value: -"States to include. Currently only the first is forwarded to the broker (single state_filter)."New value: +"States to include — any of: queued, assigned, running, completed, failed, cancelled, preempted, orphaned, scheduling_timeout. Currently only the first is forwarded to the broker (single state_filter)."
  7. First observedv0.5.5

TDQS

A4.6/5.0
Behavior4/5

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

With no annotations, the description carries the load well: it discloses the default scope (active states only), that rows are compact summaries rather than full records, and directs to the sibling for detail. It omits pagination/truncation behavior (which lives in the schema) and any permissions or rate-limit notes, so it is strong but not exhaustive.

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 purpose and default scope, then filters, then return shape, then use cases — a sensible order with no filler. It is a dense run-on paragraph, which slightly hurts scanability but wastes no sentences.

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?

No output schema exists, and the description compensates by naming the returned row fields (job_id, project, state, host, exit_code, timestamps, duration_s) so the agent knows what it gets. Combined with default scope and sibling routing, nothing essential for correct invocation is missing.

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%, so the baseline is 3, but the description adds intent-level meaning: the state filter is framed as the way to surface past runs, the finished_at window as the way to bracket history, and the default active set is restated for selection decisions. It complements rather than merely duplicates the schema.

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+resource ('List jobs on the broker with per-state counts') and immediately distinguishes itself from the sibling by naming jobd_status for full records. An agent can tell exactly what this returns versus the other jobd_* tools 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 enumerates when to use it ('what is running / queued right now?', 'what failed overnight?', 'locate a job id you've lost') and names the alternative (jobd_status) for the full-record case. That is a clear when/when-not split with no inference needed.

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