Skip to main content
Glama

sora_list_actions

List all Sora API actions and their corresponding tools to understand the full capabilities of Sora MCP. Use this reference guide to identify which tool to use for each action.

Instructions

List all available Sora API actions and corresponding tools.

Reference guide for what each action does and which tool to use.
Helpful for understanding the full capabilities of the Sora MCP.

Returns:
    Categorized list of all actions and their corresponding tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual handler function for the sora_list_actions tool. Decorated with @mcp.tool(), it returns a string listing all available Sora API actions and corresponding tools, organized by category (video generation, task management, information, workflow examples).
    @mcp.tool()
    async def sora_list_actions() -> str:
        """List all available Sora API actions and corresponding tools.
    
        Reference guide for what each action does and which tool to use.
        Helpful for understanding the full capabilities of the Sora MCP.
    
        Returns:
            Categorized list of all actions and their corresponding tools.
        """
        # Last updated: 2026-04-05
        return """Available Sora Actions and Tools:
    
    Video Generation (Version 1 - classic):
    - sora_generate_video: Create video from a text prompt (duration: 10/15/25s, size: small/large)
    - sora_generate_video_from_image: Create video from reference images (Image-to-Video)
    - sora_generate_video_with_character: Create video with a character from reference video
    - sora_generate_video_async: Create video with callback notification
    
    Video Generation (Version 2 - partner channel):
    - sora_generate_video_v2: Create video with pixel resolution (seconds: 4/8/12, size: 720x1280 etc.)
    - sora_generate_video_v2_async: Create video v2 with callback notification
    
    Task Management:
    - sora_get_task: Check status of a single generation
    - sora_get_tasks_batch: Check status of multiple generations
    
    Information:
    - sora_list_models: Show available models and their capabilities
    - sora_list_actions: Show this action reference (you are here)
    
    Workflow Examples:
    
    1. Simple Video (v1):
       sora_generate_video(prompt) → sora_get_task(task_id)
    
    2. Image-to-Video (v1):
       sora_generate_video_from_image(prompt, image_urls) → sora_get_task(task_id)
    
    3. Character-based Video (v1):
       sora_generate_video_with_character(prompt, character_url) → sora_get_task(task_id)
    
    4. Quick Video with precise resolution (v2):
       sora_generate_video_v2(prompt, seconds=8, size="1280x720") → sora_get_task(task_id)
    
    5. Async with Callback (v1 or v2):
       sora_generate_video_async(prompt, callback_url) → Wait for callback
       sora_generate_video_v2_async(prompt, callback_url) → Wait for callback
    
    Tips:
    - Video generation takes 1-2 minutes on average
    - Use async generation with callbacks for production workflows
  • core/server.py:47-55 (registration)
    The FastMCP server instance (mcp) that registers the tool via the @mcp.tool() decorator on the sora_list_actions function.
    # Initialize FastMCP server
    mcp = FastMCP(
        settings.server_name,
        icons=[Icon(src="", mimeType="image/png")],
        **mcp_kwargs,
    )
    
    logger.info(f"Initialized MCP server: {settings.server_name}")
  • main.py:188-192 (registration)
    Registration in the HTTP server card response, listing 'sora_list_actions' with description 'List available actions'.
        {"name": "sora_get_tasks_batch", "description": "Query multiple tasks"},
        {"name": "sora_list_models", "description": "List available models"},
        {"name": "sora_list_actions", "description": "List available actions"},
    ],
    "prompts": [
  • main.py:130-134 (registration)
    Startup banner printing 'sora_list_actions' as an available tool during server initialization.
    safe_print("    - sora_get_task")
    safe_print("    - sora_get_tasks_batch")
    safe_print("    - sora_list_models")
    safe_print("    - sora_list_actions")
    safe_print("")
  • Tools __init__.py imports info_tools module which contains the sora_list_actions handler, registering it with the MCP server.
    """Tools module for MCP Sora server."""
    
    # Import all tools to register them with the MCP server
    from tools import info_tools, task_tools, video_tools
    
    __all__ = [
        "video_tools",
        "task_tools",
        "info_tools",
    ]
Behavior4/5

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

No annotations provided; description discloses it returns a categorized list of actions and tools. Sufficient for a read-only, non-destructive listing tool.

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?

Three succinct sentences, front-loaded with purpose. No extraneous information.

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

Completeness5/5

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

Simple tool with no parameters and an output schema. Description fully covers its role as a reference listing.

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?

No parameters, so baseline 4 applies. Description offers no additional semantic burden beyond 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?

Explicitly states it lists all available Sora API actions and corresponding tools, serving as a reference guide. Distinct from sibling tools that focus on generation or retrieval.

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?

Indicates it is helpful for understanding capabilities, implying use for exploration. However, no explicit guidance on when to use vs. alternatives or when not to use.

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/AceDataCloud/SoraMCP'

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