Tutorial AI

List projects

list_projects

Read-only

List the Tutorial AI projects this user can access. Each project reports two independent facts: hasGeneratedVideo, true when a completed, playable render exists, and publishUrl, non-null when the project is published. Returns {projects, total, hasMore, generatedCount, publishedCount}. projects is one page, capped at 100. total counts every match after the filters; generatedCount and publishedCount count them before the filters, across every match rather than the returned page, and they overlap because a published project usually has a video too. Answer "how many" from total, generatedCount or publishedCount and never by counting the returned projects.

Input Schema

Name	Required	Description
`limit`	No	Projects per page. Defaults to 25, silently capped at 100.
`query`	No	Case-insensitive title filter
`offset`	No	Projects to skip, for reading past the first page. Defaults to 0.
`published`	No	Return only published (true) or only unpublished (false) projects. Independent of hasGeneratedVideo.
`workspaceUid`	No	Restrict results to one workspace, from list_workspaces
`hasGeneratedVideo`	No	Return only projects that have (true) or lack (false) a completed render. Counted in total before paging.

Output Schema

Name	Required	Description	Default
`total`	Yes
`hasMore`	Yes
`projects`	Yes
`generatedCount`	Yes
`publishedCount`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 30, 2026
- removedOutput schema / properties / projects / items / properties / language / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / projects / items / properties / language / type
```
Added value: +[
+  "string",
+  "null"
+]
```
- removedOutput schema / properties / projects / items / properties / publishUrl / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / projects / items / properties / publishUrl / type
```
Added value: +[
+  "string",
+  "null"
+]
```
First observedOct 15, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, but the description adds substantial behavioral detail beyond that: pagination is capped at 100, hasGeneratedVideo and publishUrl are independent facts, and generatedCount/publishedCount are computed before filters and may overlap. This is exactly the kind of return-value and counting semantics an agent needs.

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?

The purpose is front-loaded in the first sentence, and each subsequent sentence adds a distinct operational fact: field meanings, return shape, pagination cap, count derivation, and how to answer 'how many' questions. There is no filler or repetition.

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 six parameters, an output schema, and read-only annotations, this description covers what the tool returns, how pagination works, how the count fields differ from the page, and how filters affect counts. Nothing essential for correct invocation or interpretation appears to be missing.

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 every parameter already has its own documentation, including limit, query, offset, published, workspaceUid, and hasGeneratedVideo. The description does not add syntax or format details for individual parameters, so the baseline score of 3 is appropriate.

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?

The description gives a specific verb and resource: 'List the Tutorial AI projects this user can access.' The plural 'projects' and access scope make it clearly distinct from the sibling get_project tool, which retrieves a single project.

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?

It states how to answer count questions using total/generatedCount/publishedCount rather than the returned page, which is useful operational guidance. However, it does not explicitly say when to use this tool versus alternatives such as get_project, nor does it name any exclusions or prerequisites beyond the implicit listing context.

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

All Tutorial AI 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?