Skip to main content
Glama

veo_get_1080p

Retrieve the 1080p high-resolution version of a completed Veo-generated video. The video must be in 'succeeded' state before requesting.

Instructions

Get the 1080p high-resolution version of a generated video.

By default, Veo generates videos at a lower resolution for faster processing.
Use this tool to get the full 1080p version of a completed video.

Use this when:
- You need a higher resolution version for production use
- The initial video generation is complete and you want to upscale
- You need a clearer, more detailed video output

Note: The video must be in 'succeeded' state before requesting 1080p version.

Returns:
    Task ID and the 1080p video information including the new video URL.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
video_idYesThe video ID from a previous generation result. This is the 'id' field from the video data, not the task_id.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Implementation Reference

  • The main handler function for the veo_get_1080p tool. Decorated with @mcp.tool(), it accepts a video_id string, calls client.get_1080p(), and formats the result.
    @mcp.tool()
    async def veo_get_1080p(
        video_id: Annotated[
            str,
            Field(
                description="The video ID from a previous generation result. This is the 'id' field from the video data, not the task_id."
            ),
        ],
    ) -> str:
        """Get the 1080p high-resolution version of a generated video.
    
        By default, Veo generates videos at a lower resolution for faster processing.
        Use this tool to get the full 1080p version of a completed video.
    
        Use this when:
        - You need a higher resolution version for production use
        - The initial video generation is complete and you want to upscale
        - You need a clearer, more detailed video output
    
        Note: The video must be in 'succeeded' state before requesting 1080p version.
    
        Returns:
            Task ID and the 1080p video information including the new video URL.
        """
        result = await client.get_1080p(video_id)
        return format_video_result(result)
  • The HTTP client method get_1080p that sends the actual API request. Makes a POST to /veo/videos with action='get1080p' and the video_id.
    async def get_1080p(self, video_id: str) -> dict[str, Any]:
        """Get 1080p version of a video."""
        logger.info(f"📺 Getting 1080p video for: {video_id}")
        return await self.request(
            "/veo/videos", self._with_async_callback({"action": "get1080p", "video_id": video_id})
        )
  • The format_video_result helper used by the handler to format the API response into JSON with async submission guidance.
    def format_video_result(data: dict[str, Any]) -> str:
        """Format video generation result as JSON.
    
        Args:
            data: API response dictionary
    
        Returns:
            JSON string representation of the result
        """
        return json.dumps(
            _with_submission_guidance(data, "veo_get_task", "veo_get_tasks_batch"),
            ensure_ascii=False,
            indent=2,
        )
  • Type definitions used by the tool, including VideoResolution literal type (contains '1080p').
    """Type definitions for Veo MCP server."""
    
    from typing import Literal
    
    # Veo model versions
    VeoModel = Literal[
        "veo2",
        "veo2-fast",
        "veo3",
        "veo3-fast",
        "veo31",
        "veo31-fast",
        "veo31-fast-ingredients",
    ]
    
    # Aspect ratio options
    AspectRatio = Literal["16:9", "9:16", "3:4", "4:3", "1:1"]
    
    # Default model
    DEFAULT_MODEL: VeoModel = "veo2"
    
    # Video resolution options
    VideoResolution = Literal["4k", "1080p", "gif"]
    
    # Default aspect ratio
    DEFAULT_ASPECT_RATIO: AspectRatio = "16:9"
  • main.py:173-173 (registration)
    Registration of veo_get_1080p in the server card/tool listing endpoint for HTTP mode.
    {"name": "veo_get_1080p", "description": "Get 1080p version"},
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: default lower resolution, requirement for succeeded state, and return content (Task ID and 1080p video info with URL). No contradictions.

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?

Well-structured with a brief intro, bulleted usage guidance, a note, and returns section. Every sentence adds value; no waste.

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?

Given the tool's simplicity and the presence of a complete output schema (implied by return description), the description covers purpose, usage, prerequisites, and output comprehensively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with one parameter 'video_id'. The description adds crucial meaning by clarifying it is the 'id' field from video data, not the task_id, preventing common confusion.

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 tool gets the 1080p version of a generated video, with a specific verb and resource. It explains why this tool exists (default lower resolution) and provides context that distinguishes it from generic retrieval tools, though sibling differentiation is implicit rather than explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit 'Use this when' bullet points with three clear scenarios, plus a note about the required video state ('succeeded'). This gives strong guidance on when to invoke, though it does not explicitly state when not to use it.

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