BlitzReels Video Editor

List Series Content

series_content

Read-onlyIdempotent

List sources or projects in a Series. Null seriesId lists standalone content. sourceId filters projects by clip origin.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`kind`	Yes
`limit`	Yes
`offset`	Yes
`search`	Yes
`seriesId`	Yes
`sourceId`	Yes
`workspaceId`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`items`	Yes
`bounds`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 17, 2026
- removedOutput schema / properties / items / items / properties / durationSeconds / anyOf
```
Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / durationSeconds / type
```
Added value: +[
+  "number",
+  "null"
+]
```
- removedOutput schema / properties / items / items / properties / thumbnailUrl / anyOf
```
Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
```
- addedOutput schema / properties / items / items / properties / thumbnailUrl / type
```
Added value: +[
+  "string",
+  "null"
+]
```
AddedSep 10, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the description only needs to add semantic behavior. It does so by explaining that null seriesId returns standalone content and that sourceId filters projects by clip origin. No contradiction with 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 two short sentences with no filler. The primary action and scope are front-loaded, and the additional parameter guidance is compact and meaningful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema covers return structure and annotations cover safety, so those do not need elaboration. Still, with 7 required parameters and no schema descriptions, the description leaves important questions about required combinations and the meaning of kind/workspaceId unanswered. It is minimally viable but has clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and all 7 parameters are required, yet the description only clarifies seriesId and sourceId. It leaves kind, workspaceId, search, limit, and offset semantically unexplained, which is insufficient compensation for a low-coverage schema.

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') and a specific resource ('sources or projects in a Series'), and it adds a key distinguishing detail: null seriesId lists standalone content. This clearly separates it from sibling tools like series_list or series_get.

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 when to use the tool: to enumerate content within a series, and it clarifies the standalone-content case. However, it does not explicitly mention alternatives or state when not to use it, so an agent must infer the boundary against related series tools.

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?