reels

by Endroe

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

reels_render_status

Read-only

Retrieves the last render status for a project, returning the captured revision even if later edits exist.

Instructions

Read the last render status for a project. Output is the captured revision, even if later edits exist.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "projectId": "<projectId>"
    },
    "name": "reels_render_status"
  }
}

Input Schema

Name	Required	Description	Default
`projectId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 7, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely non-derivable behavior — the returned status reflects the captured revision even if later edits exist — but says nothing about the empty state, e.g. what happens when no render has ever been captured.

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?

Two short sentences with the primary action front-loaded and no filler. The second sentence is slightly opaque ('captured revision' of what), but nothing is wasted.

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?

For a one-parameter read-only status tool with no output schema, the description covers what is read and the staleness caveat, but leaves the agent guessing about the shape/possible values of the status and the no-render-yet case.

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 0%, so the description must carry the burden, and it only implies that projectId scopes to a project. It does not clarify the identifier format or the schema's pattern constraint, leaving the single parameter's meaning thin.

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?

Uses a specific verb+resource+scope: 'Read the last render status for a project.' An agent can distinguish this from a render-triggering sibling like reels_render, but the description never names that sibling explicitly to make the contrast airtight.

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?

Usage is only implied: the phrase 'last render status' and the staleness caveat suggest it is for polling/checking an existing render rather than starting one. There is no explicit when-to-use, when-not-to-use, or named alternative such as reels_render.

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