Reel Estate MCP

Official

by TryReelEstate

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

List clips

list_clips

Lists clips for the authenticated user. Filter by project ID, status, or use pagination to browse your clip library.

Instructions

Clips for the authenticated user. With projectId -> GET /clips/project/:projectId; otherwise GET /clips (the clip library) with paging/status.

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

Input Schema

Name	Required	Description	Default
`page`	No
`limit`	No
`status`	No
`projectId`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.4Jul 7, 2026

TDQS

B3.1/5.0

Behavior3/5

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

The description mentions paging and status filtering, and implies authentication via 'authenticated user'. With no annotations provided, the description carries the full burden, but it omits details like response format, rate limits, or whether the operation is read-only.

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?

The description is a single, efficient sentence that conveys key endpoint logic. It is concise and front-loaded, though the endpoint details could be slightly more structured for clarity.

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

Completeness2/5

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

Given the tool has 4 parameters, no required ones, and no output schema, the description lacks completeness. It does not explain return values, pagination boundaries, or how status filtering interacts with paging, leaving significant 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%, so the description must compensate. It only briefly mentions 'paging/status' and projectId, without explaining the meaning of each parameter (e.g., page, limit, status enum values). This is insufficient for an agent to correctly use the parameters.

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 clearly states that the tool retrieves clips for the authenticated user, with different endpoints based on the presence of a projectId. It effectively communicates the core function, but does not explicitly differentiate from sibling tools like get_clip_status or list_projects.

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 provides conditional usage guidance (with vs without projectId), implying when to use each variant. However, it does not offer explicit when-not-to-use advice or compare against alternative tools like list_movies or list_projects.

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