Skip to main content
Glama

run_job

Queue a new pipeline execution in a named or default workspace to start processing and track the resulting state.

Instructions

Queue a new run of a pipeline. Not destructive, but it does change state.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "pipeline": "<pipeline>"
    },
    "name": "run_job"
  }
}

Input Schema

NameRequiredDescriptionDefault
pipelineYes
workspaceNoNamed workspace. Omit to use the default workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

The sentence 'Not destructive, but it does change state' simply restates destructiveHint=false and readOnlyHint=false, so it adds no value beyond the annotations. Nothing is said about whether queueing twice creates duplicate runs, whether the call is async, what identifier comes back, or what permissions are needed.

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?

Two short, front-loaded sentences with no filler. The second sentence is redundant with the annotations, which slightly weakens an otherwise efficient structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a state-changing queue operation with no output schema and an undocumented required parameter, the definition should explain what is returned (e.g., a run identifier) and how to track the queued run. Neither is present, so it is incomplete relative to the tool's complexity.

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

Parameters2/5

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

Schema description coverage is only 50%: workspace is documented in the schema, but the required 'pipeline' parameter has no description anywhere. The description does not compensate by explaining the identifier format or how the pipeline is specified, leaving the single required input undocumented.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Queue a new run of a pipeline'), which is clearly distinct from siblings like get_job, cancel_job, and list_jobs. It stops short of naming any sibling or stating scope constraints explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to queue a run versus checking or canceling one, nor any prerequisite information such as whether the pipeline must exist or be enabled. The agent must infer the usage context entirely.

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