Skip to main content
Glama
IBM
by IBM

remotion_list_themes

Browse available YouTube video themes with pre-configured color palettes, typography, and motion design for tech, finance, education, gaming, and other content types.

Instructions

List available YouTube video themes.

Returns all pre-built themes optimized for YouTube videos. Each theme includes
color palettes, typography settings, and motion design tokens optimized for
specific content types (tech, finance, education, gaming, etc.).

Returns:
    JSON object with all available themes and their tokens

Example:
    themes = await remotion_list_themes()
    # Returns all themes (tech, finance, education, lifestyle, gaming, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for 'remotion_list_themes' tool. Defined as an async function decorated with @mcp.tool inside register_theme_tools. Lists available themes using ThemeManager, extracts metadata, and returns formatted JSON string.
    @mcp.tool
    async def remotion_list_themes() -> str:
        """
        List all available video themes with descriptions.
    
        Returns a list of built-in YouTube-optimized themes including their
        characteristics, primary colors, and recommended use cases.
    
        Returns:
            JSON array of themes with metadata
    
        Example:
            themes = await remotion_list_themes()
            # Returns: tech, finance, education, lifestyle, gaming, minimal, business
        """
    
        def _list():
            theme_keys = theme_manager.list_themes()
            theme_list = []
    
            for key in theme_keys:
                theme = theme_manager.get_theme(key)
                if theme:
                    theme_list.append(
                        {
                            "key": key,
                            "name": theme.name,
                            "description": theme.description,
                            "primary_color": theme.colors.primary[0]
                            if theme.colors.primary
                            else "N/A",
                            "accent_color": theme.colors.accent[0]
                            if theme.colors.accent
                            else "N/A",
                            "use_cases": theme.use_cases[:3],  # First 3 use cases
                        }
                    )
    
            return json.dumps({"themes": theme_list}, indent=2)
    
        return await asyncio.get_event_loop().run_in_executor(None, _list)
  • The registration call to register_theme_tools which defines and registers the 'remotion_list_themes' tool (and other theme tools) with the MCP server instance.
    register_theme_tools(mcp, project_manager, vfs)
  • Creation of the shared ThemeManager instance used by remotion_list_themes to access theme data.
    theme_manager = ThemeManager(vfs)
Behavior3/5

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

With no annotations provided, the description carries full burden. It discloses the return format ('JSON object with all available themes and their tokens') and content types covered ('tech, finance, education, gaming, etc.'), but doesn't mention behavioral aspects like rate limits, authentication requirements, or whether this is a read-only operation. The description adds useful context but misses some behavioral details.

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 efficiently structured with purpose first, followed by return details, and includes a practical code example. Every sentence adds value without redundancy, and the information is appropriately front-loaded with the core functionality stated immediately.

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 simplicity (0 parameters, no output schema), the description provides good coverage of what the tool does and returns. However, without annotations or output schema, it could benefit from more explicit behavioral context about the operation's characteristics (read-only, authentication needs, etc.) to be fully complete.

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?

With 0 parameters and 100% schema description coverage, the baseline is 4. The description appropriately doesn't discuss parameters since none exist, focusing instead on what the tool returns and its purpose.

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 specific action ('List available YouTube video themes') and resource ('pre-built themes optimized for YouTube videos'), distinguishing it from siblings like remotion_list_color_tokens or remotion_list_typography_tokens by focusing on complete theme packages rather than individual token types.

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 about when to use this tool ('Returns all pre-built themes optimized for YouTube videos'), but doesn't explicitly mention when not to use it or name specific alternatives among siblings like remotion_get_theme_info, leaving some guidance implicit rather than explicit.

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