Skip to main content
Glama

List jobs

list_jobs
Read-onlyIdempotent

Lists running and completed MakersMCP jobs with their output folders, helping agents check whether a prior no-result call is still running before retrying it.

Instructions

Lists the jobs makersmcp started since it was launched, running or ended, with their folders. Use it after a call that ended with no result, before starting that tool again: the job may be running. Jobs end when makersmcp ends, and a finished job's files stay in its folder.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_jobs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: job records are ephemeral and disappear when makersmcp ends, while completed jobs leave their files behind in the job folder. It does not describe ordering, truncation or pagination of the returned 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?

Three short sentences, purpose first, then usage, then lifecycle caveats — every sentence carries distinct information with no filler. The phrasing is slightly dense ("jobs makersmcp started since it was launched") but not padded.

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?

For a zero-parameter, read-only listing tool with no output schema, the description covers purpose, invocation trigger, return content (folders) and the job lifecycle. Only volume/ordering of results is left unstated, a minor gap given the simplicity.

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?

The tool takes no parameters, so there is nothing for the description to clarify; baseline is 4. No misleading parameter hints are given.

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?

"Lists the jobs makersmcp started since it was launched, running or ended, with their folders" gives a clear verb (lists), resource (jobs), scope (all jobs since launch, both running and ended) and return content (folders). It is distinguishable from siblings like wait_for_job or cancel_job by that scope, though no sibling is named explicitly.

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?

The description gives concrete when-to-use guidance: call it after a tool call returned no result, before retrying, because the job may still be running. It lacks an explicit exclusion (e.g. when to prefer wait_for_job instead), which keeps it below a 5.

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