Sceneplane

List artifacts

artifacts_list

Read-onlyIdempotent

List a project's artifacts newest-first (renders, exports, previews, audio), optionally filtered by revision or kind. Every entry carries the revision that produced it, so a lost artifact id is recoverable without walking jobs_list. Download URLs come from artifact_get.

Input Schema

Name	Required	Description
`kind`	No	Filter by kind, e.g. "render_png", "export_glb", "glb_preview"
`limit`	No	Maximum artifacts to return in this page.
`cursor`	No	Page token from a previous call's nextCursor (a row offset)
`projectId`	Yes	Stable project ID returned by project_create or projects_list.
`revisionId`	No	Only artifacts produced from this revision

Output Schema

Name	Required	Description
`items`	Yes
`projectId`	Yes	Stable project ID returned by project_create or projects_list.
`nextCursor`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 25, 2026
- removedOutput schema / properties / items / items / properties / revisionId / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / revisionId / type
```
Added value: +[
+  "string",
+  "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.3/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the description focuses on what annotations cannot say: results are newest-first, each entry carries its producing revision, and the payload does not include download URLs. Pagination behavior (the cursor/nextCursor cycle) is only implied via the schema, which keeps it short of a 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?

Three tight sentences, front-loaded with the action and scope, then the recoverability note, then the pointer to artifact_get. Every clause carries information an agent would otherwise have to infer.

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?

With annotations covering safety, a full output schema covering return shape and nextCursor, and 100% parameter coverage, the description only needs to supply ordering, filtering, and cross-tool routing — all of which it does.

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 five parameters are already documented including kind examples and the cursor's row-offset semantics. The description only restates that filtering is by revision or kind, adding no format or constraint detail beyond the schema. 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?

Specific verb and resource ('List a project's artifacts') plus the content types it covers (renders, exports, previews, audio), the ordering (newest-first) and the filter axes. It is immediately distinguishable from artifact_get, which the description explicitly defers download URLs to.

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?

It routes the agent away from two siblings with stated conditions: download URLs come from artifact_get, and recovering a lost artifact id does not require walking jobs_list. There is no explicit 'when not to use' framing, but the alternatives are named with reasons, which is more than most definitions do.

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?