Retrieve recent download jobs newest first. Use the optional status filter (scheduled, queued, downloading, done, failed, canceled) and limit to monitor or audit job progress and outcomes.
List recent jobs, newest first. status filters by comma-separated states: scheduled, queued, downloading, done, failed, canceled.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| status | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It usefully discloses sort order (newest first) and that results are bounded to "recent" jobs, but says nothing about default result count, truncation behavior, or whether older jobs are retrievable.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two tight sentences, front-loaded with purpose and sort order, followed by the one parameter detail that the schema cannot supply. No filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a two-parameter read-only list tool with no output schema, the definition covers purpose, ordering, and the filter vocabulary. The missing piece is result-size semantics (what limit actually bounds), which an agent needs to page correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the status parameter has no enum in the schema, so the description's enumeration of valid states (scheduled, queued, downloading, done, failed, canceled) and comma-separated syntax is genuinely valuable. The limit parameter, however, is left completely unexplained (no bounds, no meaning beyond the default of 20).
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ("List recent jobs") plus the ordering ("newest first"), which distinguishes it from the singular get_job sibling. It does not explicitly name siblings, so it stops short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied by the verb: an agent can infer this is for browsing recent activity. There is no explicit statement of when to prefer it over get_job or wait_for_job, and no guidance on paging through more than the default window.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.