Sceneplane

List projects

projects_list

Read-onlyIdempotent

List the account's projects, newest first, with cursor pagination.

Input Schema

Name	Required	Description
`limit`	No	Maximum number of projects to return in this page (1–50).
`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 jobs_list are keyset-paginated and do not.)
`nameFilter`	No	Optional literal project-name substring (ASCII case-insensitive); %, _ and quotes match literally.

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 / headRevisionId / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / headRevisionId / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / previewArtifactId / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / previewArtifactId / 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"
+]
```

Changed1 schema field changedOct 1, 2026

changedInput schema / properties / nameFilter / description

Previous value: -"Optional project-name filter."New value: +"Optional literal project-name substring (ASCII case-insensitive); %, _ and quotes match literally."

First observedSep 24, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds useful behavior beyond annotations: results are ordered newest first, are scoped to the account, and use cursor pagination.

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?

A single tight sentence with no waste, and it front-loads the core purpose before ordering and pagination details.

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?

The tool has an output schema, complete parameter documentation, and annotations, so the description need not explain return values. It covers the essential behavioral facts (ordering and pagination), though it omits any mention of filtering or sibling alternatives.

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%, and the schema already documents limit, cursor semantics, and nameFilter in detail. The description adds no parameter-level detail beyond saying cursor pagination, so baseline 3 is appropriate.

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?

The description states a specific verb and resource ('List the account's projects') and adds ordering. It is clear enough to distinguish from project_get/project_update siblings, but it does not explicitly name or contrast those alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Listing projects implies a context of use, but the description gives no explicit when-to-use guidance or alternatives. It does not tell the agent when to use projects_list rather than project_get or when filtering with nameFilter is appropriate.

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?