Skip to main content
Glama

List jobs

job.list
Read-onlyIdempotent

Your recent jobs, newest first, each with its status, progress and for (the media or timeline it is for), filtered by status, tool or media_id. Results are left out unless you ask (result summary or full); job.get reads one.

Input Schema

NameRequiredDescriptionDefault
toolNoOnly jobs of this tool, e.g. media.import
limitNo
resultNonone (default): each job without its result, to find one; summary: lists cut short; full: every result wholenone
statusNo
media_idNoOnly jobs for this media (importing, making or reading it)

Output Schema

NameRequiredDescriptionDefault
jobsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • addedInput schema / properties / media_id
      Added value: +{
      +  "description": "Only jobs for this media (importing, making or reading it)",
      +  "pattern": "^m_[0-9a-z]{26}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / result
      Added value: +{
      +  "default": "none",
      +  "description": "none (default): each job without its result, to find one; summary: lists cut short; full: every result whole",
      +  "enum": [
      +    "full",
      +    "summary",
      +    "none"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / tool
      Added value: +{
      +  "description": "Only jobs of this tool, e.g. media.import",
      +  "type": "string"
      +}
    • changedOutput schema / properties / jobs / items / properties / error / properties / code / enum
      Previous value: -[
      -  "bad_request",
      -  "no_audio",
      -  "not_found",
      -  "expired",
      -  "media_not_ready",
      -  "media_offline",
      -  "engine_error",
      -  "render_failed",
      -  "interrupted",
      -  "cancelled",
      -  "credential_required",
      -  "credential_invalid",
      -  "output_exists",
      -  "path_not_allowed",
      -  "limit_exceeded",
      -  "quota_exceeded",
      -  "subscription_required",
      -  "email_unverified",
      -  "service_unavailable",
      -  "server_busy"
      -]New value: +[
      +  "bad_request",
      +  "no_audio",
      +  "not_found",
      +  "expired",
      +  "media_not_ready",
      +  "media_offline",
      +  "engine_error",
      +  "render_failed",
      +  "interrupted",
      +  "stalled",
      +  "cancelled",
      +  "credential_required",
      +  "credential_invalid",
      +  "output_exists",
      +  "path_not_allowed",
      +  "limit_exceeded",
      +  "quota_exceeded",
      +  "subscription_required",
      +  "email_unverified",
      +  "service_unavailable",
      +  "server_busy"
      +]
    • addedOutput schema / properties / jobs / items / properties / for
      Added value: +{
      +  "description": "What it is for, known from the start",
      +  "properties": {
      +    "inputs": {
      +      "description": "Media it is made from",
      +      "items": {
      +        "description": "Media handle from media.import or a create.* tool",
      +        "pattern": "^m_[0-9a-z]{26}$",
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "kind": {
      +      "type": "string"
      +    },
      +    "media_id": {
      +      "description": "The media it imports, makes or reads",
      +      "pattern": "^m_[0-9a-z]{26}$",
      +      "type": "string"
      +    },
      +    "media_ids": {
      +      "description": "Stems it makes",
      +      "items": {
      +        "description": "Media handle from media.import or a create.* tool",
      +        "pattern": "^m_[0-9a-z]{26}$",
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "preset": {
      +      "type": "string"
      +    },
      +    "timeline_id": {
      +      "description": "Timeline handle; every edit returns a new one",
      +      "pattern": "^tl_[0-9a-f]{32}$",
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedOutput schema / properties / jobs / items / properties / result_summary
      Added value: +{
      +  "description": "result \"summary\": the result in brief; result \"full\" has all of it",
      +  "properties": {
      +    "cut": {
      +      "additionalProperties": {
      +        "type": "number"
      +      },
      +      "description": "Path of each cut (a.b.0.c): its full length",
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "value": {
      +      "description": "Lists cut to 5 items, long text cut"
      +    }
      +  },
      +  "required": [
      +    "value",
      +    "cut"
      +  ],
      +  "type": "object"
      +}
    • addedOutput schema / properties / jobs / items / properties / seconds_left
      Added value: +{
      +  "description": "Running: seconds left at its recent rate of progress, once it has moved steadily (later steps may differ)",
      +  "type": "number"
      +}
    • addedOutput schema / properties / jobs / items / properties / starts_in_seconds
      Added value: +{
      +  "description": "Queued next in line: seconds until a slot should free, when every job holding one has seconds_left",
      +  "type": "number"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real behavior: results are omitted by default to keep the listing light, with opt-in 'summary' or 'full'. It doesn't mention the limit cap or what happens when more jobs exist than the limit, leaving a pagination gap.

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?

One dense sentence that front-loads ordering and returned fields before the filters, with the default-exclusion rule and the sibling pointer at the end. Every clause carries information, though the phrase 'and for (the media or timeline it is for)' is awkward and slightly costly to parse.

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 described, and the description covers filtering, verbosity control, ordering and the alternative tool. The only meaningful omission is how limit interacts with result size and whether results are truncated.

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 coverage is 60% and the description reinforces the filter semantics of tool, status and media_id ('importing, making or reading it') and the three result modes. However, 'limit'—the one undocumented parameter in the schema—is never addressed in the description, so the coverage gap remains unclosed.

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 (list) and resource (jobs) plus ordering ('newest first') and the per-job fields returned (status, progress, target), then names the sibling 'job.get' that reads a single job. An agent can distinguish this from job.get and job.cancel 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 Guidelines4/5

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

Explains the workflow split: this tool finds a job, and 'job.get reads one' once you know which. It also states results are excluded by default unless requested, which shapes how to call it. It stops short of explicit when-not-to-use guidance (e.g. preferring job.get for a known id).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.