Skip to main content
Glama
IBM
by IBM

remotion_get_component_schema

Retrieve detailed schema for video components including properties, variants, animations, and usage examples to understand component structure and implementation requirements.

Instructions

Get detailed schema for a specific component.

Returns the complete schema including all properties, variants, animations,
and usage examples for a single component.

Args:
    component_name: Name of the component (e.g., "LowerThird", "TitleScene")

Returns:
    JSON object with component schema and examples

Example:
    schema = await remotion_get_component_schema(component_name="LowerThird")
    # Returns full schema for lower third component including all variants

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
component_nameYes

Implementation Reference

  • The main handler function for the 'remotion_get_component_schema' tool, decorated with @mcp.tool for automatic registration in the MCP server. It retrieves the detailed schema (as JSON) for a specified Remotion component from the COMPONENT_REGISTRY and returns it as a string. Handles missing components with an error message.
    @mcp.tool  # type: ignore[arg-type]
    async def remotion_get_component_schema(component_name: str) -> str:
        """
        Get detailed schema for a specific component.
    
        Returns the complete schema including all properties, variants, animations,
        and usage examples for a single component.
    
        Args:
            component_name: Name of the component (e.g., "LowerThird", "TitleScene")
    
        Returns:
            JSON object with component schema and examples
    
        Example:
            schema = await remotion_get_component_schema(component_name="LowerThird")
            # Returns full schema for lower third component including all variants
        """
    
        def _get_schema():
            if component_name not in COMPONENT_REGISTRY:
                return json.dumps({"error": f"Component '{component_name}' not found"})
    
            return json.dumps(COMPONENT_REGISTRY[component_name], indent=2)
    
        return await asyncio.get_event_loop().run_in_executor(None, _get_schema)
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns a JSON object with schema and examples, which is useful behavioral context. However, it does not mention potential errors (e.g., if the component doesn't exist), rate limits, authentication needs, or side effects, leaving gaps for a read operation.

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 well-structured and front-loaded, starting with the core purpose. Each sentence adds value: the first states what it does, the second details the return content, and the example illustrates usage. There is no wasted text, making it efficient and easy to parse.

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?

Given the tool's moderate complexity (single parameter, read-only operation) and lack of annotations or output schema, the description is mostly complete. It covers purpose, parameters, and return format. However, it could improve by mentioning error handling or linking to 'remotion_list_components' for valid component names, which would enhance contextual understanding.

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 0% description coverage, so the description must compensate. It adds meaning by explaining that 'component_name' is the name of a specific component and provides examples like 'LowerThird' and 'TitleScene', which clarifies usage beyond the bare schema. However, it does not detail constraints (e.g., case sensitivity) or link to sibling tools for valid values.

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 the tool's purpose with specific verb ('Get') and resource ('detailed schema for a specific component'), and distinguishes it from sibling tools like 'remotion_list_components' (which lists components) and 'remotion_search_components' (which searches). It explicitly mentions what the schema includes: properties, variants, animations, and usage examples.

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

Usage Guidelines4/5

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

The description provides clear context for when to use this tool: to retrieve detailed schema for a single component, as opposed to listing or searching components. However, it does not explicitly state when not to use it or name alternatives, such as using 'remotion_list_components' for a high-level overview instead.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/IBM/chuk-motion'

If you have feedback or need assistance with the MCP directory API, please join our Discord server