Skip to main content
Glama

veo_get_prompt_guide

Learn how to structure prompts for Veo video generation to achieve accurate, high-quality results. Includes examples and tips.

Instructions

Get guidance on writing effective prompts for Veo video generation.

Shows how to structure prompts for best video generation results.
Following these tips helps Veo understand your vision and generate
more accurate and higher quality videos.

Returns:
    Complete guide with prompt structure, examples, and tips.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The actual implementation of the veo_get_prompt_guide tool. It is an async function decorated with @mcp.tool() that returns a string containing the Veo prompt writing guide with structure, examples, camera movements, lighting, style keywords, and tips.
    @mcp.tool()
    async def veo_get_prompt_guide() -> str:
        """Get guidance on writing effective prompts for Veo video generation.
    
        Shows how to structure prompts for best video generation results.
        Following these tips helps Veo understand your vision and generate
        more accurate and higher quality videos.
    
        Returns:
            Complete guide with prompt structure, examples, and tips.
        """
        # Last updated: 2026-04-05
        return """Veo Prompt Writing Guide:
    
    ## Prompt Structure
    
    A good video prompt should include:
    1. **Subject**: What/who is in the video
    2. **Action**: What is happening or moving
    3. **Setting**: Where the scene takes place
    4. **Camera**: Camera movement or angle
    5. **Lighting**: Time of day, lighting style
    6. **Style**: Visual style or mood
    
    ## Example Prompts by Category
    
    **Product/Commercial:**
    "A white ceramic coffee mug on a glossy marble countertop, steam rising gently, soft morning sunlight streaming through a window, shallow depth of field, commercial style"
    
    **Nature/Landscape:**
    "Cinematic drone shot slowly ascending over a misty forest at sunrise, golden rays filtering through the trees, 4K quality, documentary style"
    
    **Portrait/People:**
    "Close-up of a young woman with curly hair, she turns to look at the camera and smiles warmly, natural lighting, shallow depth of field, lifestyle photography"
    
    **Abstract/Artistic:**
    "Flowing liquid metal in slow motion, iridescent colors shifting and reflecting, black background, macro lens, surreal and mesmerizing"
    
    **Action/Movement:**
    "A red sports car drifting around a corner on a mountain road, dust and smoke trailing behind, tracking shot following the car, cinematic lighting"
    
    ## Camera Movement Keywords
    
    - **Static**: Fixed camera, no movement
    - **Pan**: Camera rotates left/right
    - **Tilt**: Camera rotates up/down
    - **Zoom**: Camera zooms in/out
    - **Tracking/Following**: Camera moves with subject
    - **Dolly**: Camera moves forward/backward
    - **Crane/Aerial**: Camera moves up/down
    - **Handheld**: Slightly shaky, documentary feel
    - **Steadicam**: Smooth gliding movement
    
    ## Lighting Keywords
    
    - **Golden hour**: Warm, soft sunset/sunrise light
    - **Blue hour**: Cool, moody twilight
    - **High key**: Bright, minimal shadows
    - **Low key**: Dark, dramatic shadows
    - **Backlit**: Light from behind subject
    - **Rim lighting**: Outline of light around subject
    - **Natural light**: Realistic outdoor lighting
    - **Studio lighting**: Controlled, professional
    
    ## Style Keywords
    
    - **Cinematic**: Film-like quality
    - **Documentary**: Realistic, observational
    - **Commercial**: Clean, professional
    - **Artistic**: Creative, experimental
    - **Vintage**: Retro, nostalgic look
    - **Modern**: Contemporary, sleek
    - **Dreamy**: Soft, ethereal
    
    ## Tips for Best Results
    
    1. Be specific but not overly complex
    2. Describe motion and change, not just static scenes
    3. Include camera movement for dynamic videos
    4. Specify lighting conditions
    5. Use the translation option for non-English prompts
    6. Match aspect ratio to your intended use (16:9 for landscape, 9:16 for vertical)
    """
  • core/server.py:48-52 (registration)
    The FastMCP server instance (mcp) that registers the tool via the @mcp.tool() decorator. Imported by tools/info_tools.py to register veo_get_prompt_guide.
    mcp = FastMCP(
        settings.server_name,
        icons=[Icon(src="", mimeType="image/jpeg")],
        **mcp_kwargs,
    )
  • main.py:178-181 (registration)
    The tool is listed in the MCP server card JSON response under the HTTP transport, providing its name and description for service discovery.
    {
        "name": "veo_get_prompt_guide",
        "description": "Get prompt writing guide",
    },
  • main.py:127-127 (registration)
    The tool name is printed in the startup banner listing available tools.
    safe_print("    - veo_get_prompt_guide")
  • Integration test for veo_get_prompt_guide that calls the function and asserts the result is non-empty.
    async def test_get_prompt_guide(self) -> None:
        """Test veo_get_prompt_guide tool."""
        from tools.info_tools import veo_get_prompt_guide
    
        result = await veo_get_prompt_guide()
    
        print("\n=== Prompt Guide Result ===")
        print(result)
    
        assert len(result) > 0
Behavior4/5

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

No annotations provided, but the description accurately describes it as a read-only guide returning structured content with examples and tips, which is suitable for a non-destructive 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 clear sentences that are direct and front-loaded, with no superfluous content.

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?

Description explains purpose, expected return format (guide with structure, examples, tips), and is complete for a simple informational tool with output schema.

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 exist, so the schema fully covers the tool's inputs; description does not need to add parameter-level detail.

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?

Specifically states it provides guidance for writing effective prompts for Veo video generation, clearly distinguishing it from siblings like veo_text_to_video or veo_list_models.

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?

Clearly indicates it's for getting prompt-writing guidance, implying preparatory use before generation, though it does not explicitly state when not to use or compare with alternatives.

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/VeoMCP'

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