Sceneplane

List jobs

jobs_list

Read-onlyIdempotent

Find recent jobs in the bound deployment, optionally by project or status, including when you have lost a job ID. Read-only; returns items and an opaque nextCursor. Use job_get for one job's status/result, job_wait to await its terminal state, job_report for complete paged reports, or job_cancel to request a stop. Copy nextCursor verbatim until null.

Input Schema

Name	Required	Description
`limit`	No	Rows per page, 1-50. Default 20; values above 50 are rejected.
`cursor`	No	Opaque token — copy nextCursor VERBATIM from the previous response. NOT a row offset: "50" is rejected. (scene_inspect and artifacts_list do take integer offsets; this tool and projects_list are keyset-paginated and do not.)
`status`	No	Optional job state to filter the results.
`projectId`	No	Stable project ID returned by project_create or projects_list.

Output Schema

Name	Required	Description	Default
`items`	Yes
`nextCursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 25, 2026
- removedOutput schema / properties / items / items / properties / errorCode / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / errorCode / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / progressPct / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / progressPct / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / nextCursor / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / nextCursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedSep 24, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, and the description is consistent with that ('Read-only'). Beyond annotations it adds real value: it discloses the return shape (items plus opaque nextCursor) and the pagination termination rule ('copy nextCursor verbatim until null'). It does not discuss rate limits or result ordering, so a 4 rather than 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with purpose, then the sibling-routing sentence, then the pagination rule. Every clause carries information an agent needs; there is no filler.

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?

An output schema exists, so the description needn't explain return values, yet it still names items/nextCursor. Combined with complete sibling routing and annotation coverage of the safety profile, an agent has everything required to call it correctly.

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 description coverage is 100%, so all four parameters (limit, cursor, status, projectId) are already fully documented in the schema, including the keyset-vs-offset cursor warning. The description restates the filter intent and the cursor-copy rule but adds no semantics beyond the schema, so the baseline 3 applies.

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 and resource (list recent jobs) scoped to the bound deployment, with optional project/status filtering. It also carves out a distinct use case — recovering when a job ID has been lost — that separates it from the sibling lookup tools.

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 names the alternatives and the conditions that select them: job_get for a single job's status/result, job_wait to await terminal state, job_report for full paged reports, job_cancel to stop. This is genuine routing guidance, not inference.

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

All Sceneplane tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?