Skip to main content
Glama

get_camera_motions

Retrieve available camera motion options for video generation using Luma Dream Machine to enhance visual storytelling and dynamic content creation.

Instructions

Gets all supported camera motions

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that makes an API request to list all supported camera motions and returns them as a comma-separated string.
    async def get_camera_motions(parameters: dict) -> str:
        """Get all supported camera motions."""
        try:
            result = await _make_luma_request("GET", "/generations/camera_motion/list")
    
            if not result:
                return "No camera motions available"
    
            return "Available camera motions:\n" + ", ".join(result)
        except Exception as e:
            logger.error(f"Error in get_camera_motions: {str(e)}", exc_info=True)
            return f"Error retrieving camera motions: {str(e)}"
  • Input schema for the tool, which requires no parameters.
    class GetCameraMotionsInput(BaseModel):
        pass
  • Registration of the tool in the list_tools() function, including name, description, and input schema.
    Tool(
        name=LumaTools.GET_CAMERA_MOTIONS,
        description="Gets all supported camera motions",
        inputSchema=GetCameraMotionsInput.model_json_schema(),
    ),
  • Dispatcher case in call_tool() that routes calls to the get_camera_motions handler.
    case LumaTools.GET_CAMERA_MOTIONS:
        result = await get_camera_motions(arguments)
        return [TextContent(type="text", text=result)]
  • Enum constant defining the tool name in LumaTools.
    GET_CAMERA_MOTIONS = "get_camera_motions"
Behavior2/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 states it 'Gets' data, implying a read operation, but doesn't specify if it's safe, requires authentication, has rate limits, or what the return format might be. This leaves significant behavioral gaps for a tool with zero annotation coverage.

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 a single, efficient sentence with no wasted words. It's front-loaded with the core action and resource, making it easy to parse quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (a read operation with no parameters) and lack of annotations or output schema, the description is incomplete. It doesn't explain what 'camera motions' are in this context, what the return data looks like, or any behavioral traits, leaving the agent with insufficient context for effective use.

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, and the schema description coverage is 100% (though empty). The description adds no parameter information, which is appropriate here. A baseline of 4 is given for zero-parameter tools, as there's nothing to compensate for.

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 verb ('Gets') and resource ('all supported camera motions'), making the purpose immediately understandable. It doesn't distinguish from siblings (like 'get_generation' or 'list_generations'), but it's specific enough to understand what it retrieves.

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, context for camera motions, or how it differs from other 'get' or 'list' tools in the sibling set, leaving the agent with no usage direction.

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/bobtista/luma-ai-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server