Skip to main content
Glama
IBM
by IBM

remotion_get_theme_info

Retrieve detailed theme information including colors, gradients, typography, and motion settings for video creation projects. Use this tool to access complete design specifications for consistent visual styling across your video content.

Instructions

Get detailed information about a specific theme.

Returns all design tokens for a theme including colors, gradients,
typography, and motion settings.

Args:
    theme_name: Name of the theme (e.g., "tech", "finance", "education")

Returns:
    JSON object with theme tokens and settings

Example:
    theme = await remotion_get_theme_info(theme_name="tech")
    # Returns tech theme with blue/cyan colors and modern typography

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
theme_nameYes

Implementation Reference

  • The main handler function for the 'remotion_get_theme_info' tool. It uses ThemeManager to fetch theme information and returns it as formatted JSON, handling errors if the theme is not found.
    @mcp.tool
    async def remotion_get_theme_info(theme_name: str) -> str:
        """
        Get detailed information about a specific theme.
    
        Returns complete theme configuration including colors, typography,
        motion design, and usage recommendations.
    
        Args:
            theme_name: Theme identifier (e.g., "tech", "finance", "education")
    
        Returns:
            JSON object with complete theme information
    
        Example:
            info = await remotion_get_theme_info(theme_name="tech")
            # Returns tech theme with all design tokens
        """
    
        def _get_info():
            info = theme_manager.get_theme_info(theme_name)
    
            if not info:
                return json.dumps(
                    {
                        "error": f"Theme '{theme_name}' not found",
                        "available_themes": theme_manager.list_themes(),
                    }
                )
    
            return json.dumps(info, indent=2)
    
        return await asyncio.get_event_loop().run_in_executor(None, _get_info)
  • Registration of theme tools via the call to register_theme_tools(mcp, project_manager, vfs), which defines and registers the remotion_get_theme_info tool using the @mcp.tool decorator.
    # Register theme and token tools with virtual filesystem
    register_theme_tools(mcp, project_manager, vfs)
    register_token_tools(mcp, project_manager, vfs)
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 'all design tokens' and specifies the return format ('JSON object with theme tokens and settings'), which is helpful. However, it doesn't mention behavioral aspects like error handling (e.g., what happens if the theme doesn't exist), performance characteristics, or authentication needs. The example adds some context but is not comprehensive.

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 well-structured with a clear purpose statement, details on returns, args, and an example. It's appropriately sized (6 sentences) and front-loaded with the core functionality. The example is relevant but could be slightly more concise. No wasted sentences, though the 'Returns' section slightly repeats information from earlier.

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 moderate complexity (1 parameter, no output schema, no annotations), the description is somewhat complete but has gaps. It explains what the tool does and the parameter, but lacks details on error cases, performance, or how it fits with sibling tools. The absence of an output schema means the description should ideally elaborate more on the return structure, though it does mention 'JSON object with theme tokens and settings'.

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 schema has 1 parameter with 0% description coverage, so the description must compensate. It provides the parameter name ('theme_name'), explains its purpose ('Name of the theme'), and gives examples ('tech', 'finance', 'education'), which adds meaningful semantics beyond the bare schema. However, it doesn't specify constraints like allowed theme names or format requirements.

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 detailed information about a specific theme' and specifies what information is returned ('all design tokens for a theme including colors, gradients, typography, and motion settings'). It distinguishes from siblings like 'remotion_list_themes' (which likely lists theme names rather than detailed info) and 'remotion_list_color_tokens' (which focuses on specific token types). However, it doesn't explicitly contrast with 'remotion_get_info' or 'remotion_get_composition_info', which might have overlapping functionality.

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 when detailed theme information is needed, as opposed to just listing themes (via 'remotion_list_themes'). The example suggests using it to retrieve a specific theme's design tokens. However, it lacks explicit guidance on when to use this versus other info-fetching tools like 'remotion_get_info' or 'remotion_get_composition_info', and doesn't mention prerequisites or error conditions.

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