Skip to main content
Glama
IBM
by IBM

remotion_get_info

Retrieve server version, capabilities, and statistics about available video components, themes, and tools in the Remotion Video Generator system.

Instructions

Get information about the Remotion MCP Server.

Returns server version, capabilities, and statistics about available
components, themes, and tools.

Returns:
    JSON object with server information

Example:
    info = await remotion_get_info()
    # Returns server version, component count, theme count, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function for the 'remotion_get_info' tool. Decorated with @mcp.tool for automatic registration in the MCP server. Returns JSON with server info, version, and statistics on components, themes, and categories.
    @mcp.tool  # type: ignore[arg-type]
    async def remotion_get_info() -> str:
        """
        Get information about the Remotion MCP Server.
    
        Returns server version, capabilities, and statistics about available
        components, themes, and tools.
    
        Returns:
            JSON object with server information
    
        Example:
            info = await remotion_get_info()
            # Returns server version, component count, theme count, etc.
        """
    
        def _get_info():
            info = {
                "name": "chuk-motion",
                "version": "0.1.0",
                "description": "AI-powered video generation with design system approach",
                "statistics": {
                    "components": len(COMPONENT_REGISTRY),
                    "themes": len(YOUTUBE_THEMES),
                    "categories": len({c.get("category") for c in COMPONENT_REGISTRY.values()}),
                },
                "categories": list({c.get("category") for c in COMPONENT_REGISTRY.values()}),
            }
            return json.dumps(info, indent=2)
    
        return await asyncio.get_event_loop().run_in_executor(None, _get_info)
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 what the tool returns (server information including version, capabilities, statistics) and provides a usage example, which adds useful context. However, it doesn't mention potential limitations, error conditions, authentication requirements, or performance characteristics that would be helpful for an agent.

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 appropriately sized. It starts with the core purpose, specifies what information is returned, provides a clear return format description, and includes a practical usage example. Every sentence adds value without redundancy. The information is front-loaded with the most important details first.

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?

Given the tool's simplicity (no parameters, no annotations, no output schema), the description provides adequate coverage of what the tool does and what it returns. However, for a server information tool, additional context about when this information might be useful (e.g., for debugging, capability checking, or monitoring) would improve completeness. The example helps but doesn't fully compensate for the lack of usage context.

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 tool has zero parameters (schema coverage 100%), so the baseline score is 4. The description appropriately doesn't waste space discussing non-existent parameters. The example shows the tool being called without arguments, which reinforces the parameterless nature.

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: 'Get information about the Remotion MCP Server' and specifies what information it returns (server version, capabilities, statistics about components, themes, and tools). It distinguishes itself from sibling tools by focusing on server metadata rather than specific operations like creating projects or listing components. However, it doesn't explicitly contrast with similar tools (though none appear to directly overlap).

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, timing considerations, or relationships to other tools. While the purpose is clear, there's no explicit 'when-to-use' context that would help an agent decide between this and other informational tools like remotion_get_composition_info or remotion_get_theme_info.

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