gemini-media-mcp

Overview Schema Source Related Servers Discussions Admin

Edit video

edit_video

Change an existing video clip with a text instruction to add, remove, replace, restyle, relight, or swap background, keeping all else unchanged.

Instructions

Change an existing clip with an instruction (add, remove or replace objects, restyle, relight, change the background) with Gemini Omni Flash, keeping everything else. Pass the jobId of a finished clip (Omni clips are edited in conversation) or a video file of at most 10 s. Asynchronous like generate_video; about $0.10 per second of video at 720p.

Input Schema

TableJSON Schema

Name	Required	Description
`jobId`	No	A completed video job to edit. Omni clips are edited in conversation (Google keeps the context); other clips are sent as their saved file. Pass jobId or video.
`model`	No	Model ID or alias; default omni (the only model that edits videos).
`video`	No	Or a video file to edit: file path, gemini-media:// URI or data: URI. At most 10 seconds and 20 MB.
`prompt`	Yes	The change, stated simply, ending with 'Keep everything else the same.' (e.g. 'Make the phone invisible. Keep everything else the same.')
`outputName`	No	Optional base file name for the saved video. Defaults to the source name plus -edit.
`resolution`	No	360p, 720p (default), 1080p or 4k (1080p and 4k are upscaled).
`waitSeconds`	No	Block up to this many seconds for the result (default 0 = return a job handle immediately). Keep under your client's tool timeout.
`approvedCostUsd`	No	Only needed above the confirmation threshold: the cost in USD the user approved.
`referenceImages`	No	Optional images to bring into the clip; refer to them as <IMAGE_REF_0>, <IMAGE_REF_1>... in the prompt.

Output Schema

TableJSON Schema

Name	Required	Description
`cost`	Yes
`next`	No	Suggested next step
`error`	No
`files`	No
`jobId`	Yes	Opaque handle; pass it to get_video, extend_video or edit_video
`model`	Yes
`state`	Yes	working, completed, failed or filtered
`warnings`	No
`elapsedSeconds`	Yes
`remoteExpiresAt`	No	When Google deletes the server-side copy; extend before this time

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.0Oct 14, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds rich context beyond annotations: asynchronous behavior like generate_video, cost of ~$0.10/second at 720p, the <=10s input limit, and the conversational editing model for Omni clips. This goes well beyond the readOnly/destructive hints.

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?

Three dense sentences, front-loaded with the core action and editing capabilities, followed by input constraints and async/cost details. Efficient, though the parenthetical enumeration and cost clause make it slightly heavy.

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?

For a 9-parameter async mutation tool with full schema and an output schema present, the description covers the essential agent-facing facts: purpose, input source, duration limit, async nature, and cost. Nothing material is missing.

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

Parameters3/5

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

Schema coverage is 100%, so parameters are already fully documented in the schema. The description adds some value by mentioning jobId vs video and the 10s cap, but largely repeats schema content; baseline 3 is appropriate.

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?

States a specific verb (edit) and resource (existing clip), enumerates the kinds of edits supported, and names the model and siblings it relates to (generate_video). An agent can distinguish it from generate_video, extend_video, and edit_image without opening schemas.

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?

Explains when to use: to change an existing clip while keeping everything else, and clarifies the two input sources (jobId of a finished clip or a video file). It lacks explicit when-not-to-use guidance (e.g. when to prefer extend_video or edit_image), keeping it below 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server