Skip to main content
Glama
IBM
by IBM

remotion_list_motion_tokens

List available motion design tokens including spring configurations, easing curves, and duration presets for creating professional animations in video production.

Instructions

List all available motion design tokens.

Returns spring configurations, easing curves, and duration presets
for creating smooth, professional animations.

Returns:
    JSON object with motion tokens (springs, easings, durations)

Example:
    motion = await remotion_list_motion_tokens()
    # Returns spring configs, easing curves, duration presets

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'remotion_list_motion_tokens' MCP tool. Defined inside register_token_tools(), decorated with @mcp.tool, and returns JSON-serialized MOTION_TOKENS.
    @mcp.tool
    async def remotion_list_motion_tokens() -> str:
        """
        List all available motion design tokens.
    
        Returns spring configurations, easing curves, duration presets,
        animation presets, and YouTube optimization guidelines.
    
        Returns:
            JSON object with complete motion system
    
        Example:
            motion = await remotion_list_motion_tokens()
            # Returns springs, easings, durations, animation presets
        """
    
        def _list():
            return json.dumps(MOTION_TOKENS.model_dump(), indent=2)
    
        return await asyncio.get_event_loop().run_in_executor(None, _list)
  • Registers all token tools (including remotion_list_motion_tokens) by calling register_token_tools(mcp, project_manager, vfs) after importing it.
    from .tools.token_tools import register_token_tools
    from .utils.project_manager import ProjectManager
    
    logging.basicConfig(level=logging.INFO)
    logger = logging.getLogger(__name__)
    
    # Create the MCP server instance
    mcp = ChukMCPServer("chuk-motion")
    
    # Create virtual filesystem instance (using file provider for actual file operations)
    vfs = AsyncVirtualFileSystem(provider="file")
    
    # Create project manager instance
    project_manager = ProjectManager()
    
    # Register composition builder methods dynamically from components
    register_all_builders(CompositionBuilder)
    register_all_renderers(CompositionBuilder)
    
    # Register theme and token tools with virtual filesystem
    register_theme_tools(mcp, project_manager, vfs)
    register_token_tools(mcp, project_manager, vfs)
  • Imports MOTION_TOKENS used by the tool handler to provide the motion token data.
    from ..tokens.token_manager import TokenManager
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 motion tokens in a JSON object, which is useful behavioral context. However, it doesn't cover aspects like rate limits, authentication needs, or error handling, leaving gaps for a tool with no annotation support.

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 the core purpose. The example adds clarity without redundancy. However, the 'Returns:' section slightly repeats information from the first sentence, making it less than perfectly efficient.

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 no annotations, no output schema, and 0 parameters, the description is adequate but has gaps. It explains the return content and includes an example, but lacks details on response structure, error cases, or integration with sibling tools, making it minimally viable for a simple listing tool.

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 0 parameters with 100% schema description coverage, so the baseline is high. The description adds value by clarifying that no inputs are needed and providing an example usage, which compensates for the lack of parameter documentation beyond the schema.

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 verb ('List') and resource ('all available motion design tokens'), distinguishing it from siblings like remotion_list_color_tokens or remotion_list_typography_tokens by focusing on motion-specific tokens. It explicitly defines what motion tokens include: spring configurations, easing curves, and duration presets.

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?

No explicit guidance on when to use this tool versus alternatives is provided. While the description implies usage for animation design, it doesn't specify prerequisites, compare to other listing tools, or indicate scenarios where this tool is preferred over others. The context is clear but lacks actionable usage rules.

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