Skip to main content
Glama
fabdendev

dagster-mcp

by fabdendev
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

list_jobs

Explore jobs across code locations with optional filters by repository or location to retrieve job names, descriptions, and context for launching pipelines.

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. Dates show when Glama detected each change.

  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.9/5.0
Behavior5/5

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

With zero annotations, the description carries the full burden — and it delivers thoroughly. It discloses the raise-vs-empty behavior on broken/loading locations, the distinction between filtered and unfiltered calls, and the exact-match filter semantics. This is precisely the behavioral context an agent needs to avoid misinterpreting empty results.

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?

Well-structured: purpose and return value are front-loaded, followed by filter semantics, error behavior, and a closing when-to-use. Every sentence adds information; the only minor deduction is that the error-handling paragraph could be tightened slightly without losing meaning.

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?

Comprehensive for a filtered-list tool with an output schema. The description covers purpose, filter semantics, error behavior, load-health redirection, and usage context. With an output schema present to document return fields, nothing an agent needs to call this tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, but the description compensates fully: it explains that repository_name and location_name are independent exact-match filters, that both must match when supplied together, and that no-filters lists everything loaded. The env parameter is the only one not explicitly discussed, but its role is implied by the tool context.

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?

The description states a specific verb ('List') and resource ('jobs across code locations'), describes the return payload (repository name, code location name, job name, description), and differentiates itself from siblings like list_code_locations and launch_job. An agent can immediately tell what this tool does and how it differs.

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 states 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'), and gives detailed context on filter behavior and the error-raising condition. It also directs the user to list_code_locations or get_instance_status for load-health checks, effectively routing to alternatives.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/fabdendev/dagster-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server