Reel Estate MCP

Official

Overview Schema Source Related Servers Discussions Admin

How to use this server (start-to-finish walkthrough)

help

Guided walkthrough of the full property video pipeline: sign-in, project creation, photo editing, animation, audio, arranging, and rendering. Includes example args and gotchas. Use this first if unsure where to start.

Instructions

Guided, numbered walkthrough of the whole pipeline — sign in → create a project → add photos → edit → animate clips → add music/voiceover/overlays → arrange → render — with example args and the gotchas (async polling, paid gating). Call this first if you're not sure where to start.

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": "help"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.4Jul 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It reveals that the tool includes example arguments and mentions key gotchas (async polling, paid gating). However, it does not fully detail the exact interactive flow or output format, but for a help tool, this is adequate.

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, front-loaded sentence that efficiently conveys the tool's purpose and usage guidance. It is concise for its informational load, though it could be slightly restructured for readability (e.g., breaking into two sentences).

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?

Given that the tool has no parameters and no output schema, the description fully covers what the tool does: a walkthrough with pipeline steps, example args, and gotchas. There is no missing information for an agent to decide on invocation.

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

Parameters4/5

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

The input schema has zero parameters with 100% schema description coverage, so no additional parameter info is needed. The description's mention of 'example args' refers to content within the walkthrough, not tool parameters, which is fine. No further semantic burden.

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 clearly states it is a 'Guided, numbered walkthrough of the whole pipeline', specifying the verb 'walkthrough' and the resource 'this server'. It distinguishes itself from sibling tools by mentioning the comprehensive pipeline steps, which no other tool covers.

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

Usage Guidelines5/5

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

The description explicitly says 'Call this first if you're not sure where to start', providing clear guidance on when to use this tool. It also outlines the pipeline steps and notes gotchas (async polling, paid gating), helping the agent decide when to invoke it.

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