Skip to main content
Glama
fabdendev

dagster-mcp

by fabdendev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

List Jobs

list_jobs

List jobs across Dagster code locations, optionally filtered by repository or location, to explore available jobs and find names needed to launch them.

Instructions

List jobs across code locations, optionally filtered by repository or location.

Returns per job: repository name, code location name, job name, and description. repository_name and location_name are independent exact-match filters; when both are supplied, a job must match both.

An empty result when filtering means no match was found among loaded code locations. If a code location relevant to the filter failed to load or is still loading, list_jobs raises instead of silently reporting no jobs — check list_code_locations for details. Calling with no filters lists whatever is loaded and never raises for a broken location; use list_code_locations or get_instance_status to check load health directly.

When to use: as a starting point to explore what jobs exist, or to find the exact job name and repository_location needed for launch_job.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
envNo
location_nameNo
repository_nameNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv0.10.0
    • addedInput schema / properties / location_name
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • addedInput schema / properties / repository_name
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}
    • removedOutput schema / properties / result / items / additionalProperties
      Removed value: -true
    • addedOutput schema / properties / result / items / description
      Added value: +"Public job metadata returned by :func:`list_jobs`."
    • addedOutput schema / properties / result / items / properties
      Added value: +{
+  "description": {
+    "type": "string"
+  },
+  "job": {
+    "type": "string"
+  },
+  "location": {
+    "type": "string"
+  },
+  "repository": {
+    "type": "string"
+  }
+}
    • addedOutput schema / properties / result / items / required
      Added value: +[
+  "repository",
+  "location",
+  "job",
+  "description"
+]
  2. First observedv0.8.0

TDQS

A4.5/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that filtered calls raise when a relevant code location failed to load or is still loading, while an unfiltered call never raises. It also defines empty-result semantics, though it omits pagination or read-only confirmation beyond the implied 'List'.

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 core purpose and the returned fields, then filtering semantics, then edge cases, then usage. Every sentence is substantive, with only minor repetition around 'check list_code_locations' appearing twice.

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 needn't be documented, yet the description usefully names the per-job fields anyway. Filtering, error behavior, and usage are all covered; only the env parameter and pagination behavior remain unaddressed.

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 description coverage is 0%, so the description must compensate, and it does for two of three params: repository_name and location_name are independent exact-match filters that combine with AND semantics. The env parameter is never explained in either schema or description, which is the remaining gap.

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 ('List jobs across code locations') plus the optional filter dimensions. It also names the related siblings (list_code_locations, get_instance_status, launch_job) so the agent can distinguish this from its neighbors without opening any 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?

Has an explicit 'When to use' section: as a starting point to explore jobs, or to find the exact job name and repository_location needed for launch_job. It also clarifies the alternative path (use list_code_locations or get_instance_status to check load health), leaving nothing to inference.

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