BlitzReels Video Editor

List Projects

projects_list

Read-onlyIdempotent

List the user's BlitzReels projects with status, duration, and basic metadata.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of projects to return (1-50)
`offset`	No	Project offset.
`search`	No	Search projects by name
`status`	No	Filter by project status	active
`workspaceId`	No	Optional workspace ID. Defaults to the user's default workspace. UUID string.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`bounds`	Yes
`projects`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedAug 26, 2026

addedOutput schema / properties / projects / items / additionalProperties
```
Added value: +false
```

addedOutput schema / properties / projects / items / properties

Added value: +{
+  "clipCount": {
+    "type": "number"
+  },
+  "description": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "durationSeconds": {
+    "type": "number"
+  },
+  "id": {
+    "type": "string"
+  },
+  "lastExportAt": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "name": {
+    "type": "string"
+  },
+  "projectUrl": {
+    "type": "string"
+  },
+  "status": {
+    "enum": [
+      "ready",
+      "exporting",
+      "needs_captions",
+      "processing"
+    ],
+    "type": "string"
+  },
+  "thumbnailUrl": {
+    "type": [
+      "string",
+      "null"
+    ]
+  },
+  "updatedAt": {
+    "type": "string"
+  }
+}

addedOutput schema / properties / projects / items / required

Added value: +[
+  "id",
+  "name",
+  "description",
+  "updatedAt",
+  "lastExportAt",
+  "durationSeconds",
+  "clipCount",
+  "thumbnailUrl",
+  "status",
+  "projectUrl"
+]

First observedAug 5, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already cover the safety profile with readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that results include status, duration, and metadata, but does not disclose default status filtering (active) or workspace fallback behavior. It is not misleading and adds mild value beyond the annotations.

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 description is a single sentence with no filler. It front-loads the action and resource and usefully names the key return fields, making it immediately scannable and informative.

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?

For a straightforward list tool, the description is adequate given the fully documented schema, an output schema, and comprehensive annotations. It does not mention pagination or filter defaults, but those are captured in the input schema, so nothing essential is missing for an agent to call the tool 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%, with each of the 5 parameters documented in detail, including constraints, enums, and defaults. The description adds no parameter-level meaning beyond what the schema already provides, 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 uses a specific verb ('List') with a clear resource ('the user's BlitzReels projects') and states the returned information ('status, duration, and basic metadata'). This distinguishes it from sibling tools like projects_get and projects_inspect, which handle single-project retrieval or deeper inspection.

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?

The description implies a listing use case but does not explicitly explain when to use projects_list versus alternatives such as projects_get, projects_inspect, or projects_create. No exclusions or conditions are provided, so an agent must infer selection from the tool name and sibling context.

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

All BlitzReels Video Editor 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?