Skip to main content
Glama
IBM
by IBM

remotion_list_components

Discover available video components for creating professional YouTube videos. Browse categorized building blocks with schemas, properties, and usage examples to plan your video composition.

Instructions

List available Remotion video components with their schemas.

Returns all available components organized by category. Each component
includes its variants, properties, and usage examples. This helps LLMs
discover what building blocks are available for video creation.

Args:
    category: Optional category filter (scene, overlay, animation, chart, layout)
             If not specified, returns all categories

Returns:
    JSON object with component definitions organized by category

Example:
    components = await remotion_list_components()
    # Returns all available components

    overlay_components = await remotion_list_components(category="overlay")
    # Returns only overlay components (lower thirds, captions, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNo

Implementation Reference

  • The handler function for the 'remotion_list_components' MCP tool. Decorated with @mcp.tool for automatic registration with the MCP server. Retrieves components from COMPONENT_REGISTRY, filters by optional category, and returns pretty-printed JSON.
    @mcp.tool  # type: ignore[arg-type]
    async def remotion_list_components(category: str | None = None) -> str:
        """
        List available Remotion video components with their schemas.
    
        Returns all available components organized by category. Each component
        includes its variants, properties, and usage examples. This helps LLMs
        discover what building blocks are available for video creation.
    
        Args:
            category: Optional category filter (scene, overlay, animation, chart, layout)
                     If not specified, returns all categories
    
        Returns:
            JSON object with component definitions organized by category
    
        Example:
            components = await remotion_list_components()
            # Returns all available components
    
            overlay_components = await remotion_list_components(category="overlay")
            # Returns only overlay components (lower thirds, captions, etc.)
        """
    
        def _list():
            if category:
                filtered = {
                    name: comp
                    for name, comp in COMPONENT_REGISTRY.items()
                    if comp.get("category") == category
                }
                return json.dumps(filtered, indent=2)
            return json.dumps(COMPONENT_REGISTRY, indent=2)
    
        return await asyncio.get_event_loop().run_in_executor(None, _list)
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the return format ('JSON object with component definitions organized by category') and includes examples, which adds value. However, it lacks details on potential limitations (e.g., rate limits, authentication needs, or error handling), which would be helpful for a tool with no annotation coverage.

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 appropriately sized and front-loaded, starting with a clear purpose statement. The additional sentences and examples add value without unnecessary verbosity. However, the structure could be slightly improved by more explicitly separating usage guidance from parameter details.

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 low complexity (1 optional parameter, no output schema, no annotations), the description is reasonably complete. It covers the purpose, parameter semantics, return format, and includes examples. For a simple list tool, this provides adequate context, though adding more behavioral details (e.g., on errors or performance) would enhance completeness.

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 1 parameter with 0% description coverage, so the description must compensate. It adds meaning by explaining the 'category' parameter as an 'Optional category filter' with specific values (scene, overlay, animation, chart, layout) and provides examples. This significantly enhances understanding beyond the bare schema, though it doesn't cover all possible edge cases.

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 the tool's purpose: 'List available Remotion video components with their schemas.' It specifies the verb ('List'), resource ('Remotion video components'), and what information is included ('schemas'). However, it doesn't explicitly differentiate from sibling tools like 'remotion_search_components' or 'remotion_get_component_schema', which appear to have related but distinct purposes.

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 implies usage context through the statement 'This helps LLMs discover what building blocks are available for video creation,' suggesting it's for discovery purposes. It provides an example with an optional category filter but doesn't explicitly state when to use this tool versus alternatives like 'remotion_search_components' or 'remotion_get_component_schema,' leaving some ambiguity.

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