Skip to main content
Glama
IBM
by IBM

remotion_search_components

Search for video components by name or description to find the right elements for your Remotion video projects when you know what you need but not the exact component name.

Instructions

Search for components by name or description.

Performs a case-insensitive search across component names and descriptions.
Useful when you know what you want but not the exact component name.

Args:
    query: Search term to match against component names and descriptions

Returns:
    JSON object with matching components and their details

Example:
    results = await remotion_search_components(query="text")
    # Returns all components with "text" in name or description
    # (TitleScene, TextOverlay, TextAnimation, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes

Implementation Reference

  • The primary handler implementation for the 'remotion_search_components' tool. This async function searches the COMPONENT_REGISTRY for components matching the query in name, description, or category, and returns results as formatted JSON. The @mcp.tool decorator registers it as an MCP tool.
    @mcp.tool  # type: ignore[arg-type]
    async def remotion_search_components(query: str) -> str:
        """
        Search for components by name or description.
    
        Performs a case-insensitive search across component names and descriptions.
        Useful when you know what you want but not the exact component name.
    
        Args:
            query: Search term to match against component names and descriptions
    
        Returns:
            JSON object with matching components and their details
    
        Example:
            results = await remotion_search_components(query="text")
            # Returns all components with "text" in name or description
            # (TitleScene, TextOverlay, TextAnimation, etc.)
        """
    
        def _search():
            query_lower = query.lower()
            results = {}
    
            for name, comp in COMPONENT_REGISTRY.items():
                # Search in component name
                if query_lower in name.lower():
                    results[name] = comp
                    continue
    
                # Search in description
                if query_lower in comp.get("description", "").lower():
                    results[name] = comp
                    continue
    
                # Search in category
                if query_lower in comp.get("category", "").lower():
                    results[name] = comp
    
            return json.dumps(results, indent=2)
    
        return await asyncio.get_event_loop().run_in_executor(None, _search)
  • The @mcp.tool decorator on the handler function registers 'remotion_search_components' as an available MCP tool.
    @mcp.tool  # type: ignore[arg-type]
Behavior4/5

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

With no annotations provided, the description carries full burden and discloses key behavioral traits: 'Performs a case-insensitive search across component names and descriptions.' It also provides a concrete example of what gets returned. However, it doesn't mention rate limits, authentication needs, or pagination behavior.

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?

Well-structured with purpose statement, behavioral detail, usage guidance, parameter explanation, return value description, and concrete example. Every sentence adds value, and information is front-loaded appropriately.

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 single-parameter search tool with no annotations and no output schema, the description provides good coverage: purpose, usage context, parameter semantics, and example. However, it doesn't detail the exact structure of the returned JSON object, which would be helpful given no output schema exists.

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

Parameters5/5

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

The description adds significant meaning beyond the bare schema (0% coverage). It explains the 'query' parameter's purpose ('Search term to match against component names and descriptions'), search behavior ('case-insensitive'), and provides an example showing how it's used.

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 ('Search') and resource ('components'), specifying search scope ('by name or description'). It distinguishes from sibling tools like 'remotion_list_components' by emphasizing search functionality rather than listing.

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?

Explicitly states when to use this tool: 'Useful when you know what you want but not the exact component name.' This provides clear context for choosing this over alternatives like 'remotion_list_components' or 'remotion_get_component_schema'.

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