VideoGen

List projects

list_projects

Read-onlyIdempotent

Browse projects in the authenticated team, including dashboard-created projects, most recently updated first. Returns project ids, titles, status, editor URLs, timestamps, and aspect ratios with a pagination cursor.

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_projects"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of items to return.
`cursor`	No	Pagination cursor from a previous response's `nextCursor`.
`selfOnly`	No	When true, restrict results to items created by the API key owner rather than the whole team.

Output Schema

Name	Required	Description
`hasMore`	Yes	Whether another page is available.
`projects`	Yes	Projects, most recently updated first.
`nextCursor`	Yes	Cursor for the next page, or null when hasMore is false.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 4, 2026
- removedOutput schema / properties / nextCursor / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / nextCursor / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / projects / items / properties / assistantId / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / projects / items / properties / assistantId / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedOct 9, 2026

TDQS

A3.8/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-redundant behavior: result scope includes dashboard-created projects, results are most-recently-updated first, and the response carries a pagination cursor.

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?

Two tight sentences: the first front-loads scope and ordering, the second covers returns and pagination. There is no filler, hedging, or repetition.

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?

An output schema exists, so enumerating returned fields is mildly redundant, but it usefully reinforces scope and sort order. The only real gap is that the description never mentions the selfOnly owner-vs-team toggle, leaving that entirely to the schema for a tool whose whole point is team-wide browsing.

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 three parameters (limit, cursor, selfOnly) are already documented in the schema, making 3 the baseline. The description only echoes the pagination cursor concept and adds nothing about limit bounds or the team-vs-owner distinction that selfOnly controls.

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 gives a specific verb ('Browse'), resource ('projects'), and scope ('in the authenticated team, including dashboard-created projects'), plus ordering. Plural 'projects' plus 'Browse' clearly separates it from the singular sibling get_project, but no other sibling (e.g., list_project_remix_actions) is named to sharpen the boundary.

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?

Usage context is implied by 'Browse projects in the authenticated team' and the default sort order, but there is no explicit when-to-use versus when-to-use-get_project statement and no guidance on when to set selfOnly. An agent can infer the use case but must reason about alternatives itself.

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

All VideoGen 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.