Skip to main content
Glama

veo_video_objects

Insert objects into or remove objects from videos by specifying a region. Precisely modify video areas using optional masks.

Instructions

Insert or remove objects in a video.

Modifies a generated video by adding or removing objects in specific regions.

Use this when:
- You want to add a new object to an existing video
- You need to remove an unwanted object from a video
- You want to precisely modify specific areas of a video

Returns:
    Task ID and modified video information including URLs and state.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
video_idYesThe video ID from a previous generation result. Use the 'id' field from the video data.
actionYes'insert' adds a new object to the video. 'remove' deletes an object from a specific area.
promptNoFor 'insert': describes what object to add (strongly recommended). For 'remove': describes what to remove (optional). If omitted for insert, the API may reject the request.
image_maskNoOptional mask image URL where white pixels indicate the region to operate on. Providing a mask improves precision for both insert and remove operations.
callback_urlNoOptional URL to receive a POST callback when the operation completes.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries full burden. It mentions modification and return of Task ID and video info, but lacks details on destructiveness, authentication requirements, or error behavior. Adequate but not thorough.

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 structured with clear sections and bullet points. It is reasonably concise, though some details (e.g., return info) could be integrated into the flow to reduce repetition.

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

Completeness4/5

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

Given 5 parameters, 2 required, and existence of output schema, the description provides sufficient context for use. It covers purpose, usage, and return, but lacks behavioral properties like processing time or idempotency.

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?

Schema coverage is 100%, so parameters are well-documented. The description adds value by explaining the action enum (insert/remove) and that prompt is strongly recommended for insert, which goes 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 it inserts or removes objects in a video, using specific verbs and resource. It distinguishes itself from sibling tools like veo_text_to_video or veo_extend_video, which handle different operations.

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?

The description provides explicit 'Use this when:' scenarios listing three use cases. However, it does not mention when not to use the tool or suggest alternatives, which would improve decision-making.

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