Skip to main content
Glama
Sign In

Remocn: Remotion MCP server

by dev.remocn
OverviewDiscussionsAdmin

Search Remocn components

search_components
Read-onlyIdempotent

Search Remocn Remotion components by what they do. Returns name, docs .md URL, vibe, length (frames @30fps), use/avoid notes and install command.

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": {
      "query": "<query>"
    },
    "name": "search_components"
  }
}

Input Schema

NameRequiredDescriptionDefault
vibeNoTonal tag to match the brand
limitNo
queryYesWhat the component should do, e.g. 'typewriter headline'
maxLengthNoMax motion length in frames @30fps

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the safety profile needs no restating. The description earns credit by enumerating what comes back (name, docs .md URL, vibe, length in frames @30fps, use/avoid notes, install command), which matters because no output schema exists. It omits ranking/relevance behavior and any default for limit.

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?

Two sentences, purpose first, return payload second, with zero filler. Every clause carries information the agent can act on.

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?

For a four-parameter search tool with no output schema, the description covers intent and result shape adequately. Remaining gaps are minor conveniences (default limit, result ordering, whether vibe filters or just boosts) rather than things that would cause a mis-call.

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 coverage is 75% and query and maxLength already carry descriptions, so the baseline is 3. The description usefully pins the length unit to frames @30fps, matching maxLength, but it says nothing about how limit defaults or how the vibe enum interacts with free-text query, and reusing the word "vibe" for a returned field muddies the parameter meaning.

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?

"Search Remocn Remotion components by what they do" gives a specific verb plus resource and a matching basis (behavior described in natural language), which distinguishes it from get_component-style lookup by identifier. It stops short of naming a sibling explicitly, so the differentiation is inferable rather than stated.

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?

"by what they do" implicitly tells the agent to use this when it knows the desired behavior rather than a component name, which is useful implied guidance. There is no explicit when-not, no mention of what to do with results (e.g., preview or get by name), and no note on how to combine the query with the vibe filter.

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

All Remocn: Remotion MCP server toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources