Skip to main content
Glama

BlitzReels Video Editor

by com.blitzreels
OverviewDiscussionsAdmin

List Projects

projects_list
Read-onlyIdempotent

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of projects to return (1-50)
offsetNoProject offset.
searchNoSearch projects by name
statusNoFilter by project statusactive
workspaceIdNoOptional workspace ID. Defaults to the user's default workspace. UUID string.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
boundsYes
projectsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / projects / items / properties / status / enum
      Previous value: -[
-  "ready",
-  "exporting",
-  "needs_captions",
-  "processing"
-]New value: +[
+  "ready",
+  "exporting",
+  "needs_captions",
+  "processing",
+  "failed"
+]
  2. Changed3 schema fields changed
    • 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"
+]
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare the full safe-read profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the safety burden is covered. The description adds the returned fields but says nothing about pagination behavior or defaults despite limit/offset being present.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single tight sentence with the resource and returned fields front-loaded. No wasted words, though it is arguably too terse given the available parameter surface.

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?

With a full output schema and complete annotations, an agent has enough to call this correctly; the returned fields are even summarized. Only the lack of sibling disambiguation and pagination notes keeps it from being fully complete.

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 in the schema, including the status enum and workspaceId default. The description adds no parameter-level meaning beyond that baseline.

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?

States a specific verb (List) and resource (projects) and even names what each item carries: status, duration, and basic metadata. It does not differentiate itself from close siblings like projects_get or projects_inspect, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of alternatives (projects_get, projects_inspect), and no note on pagination or default scoping. An agent must infer all of this from the schema.

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 toolsInspect
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