google-flow-mcp

Overview Schema Source Related Servers Discussions Admin

Create a Scenebuilder scene

flow_create_scene

Creates a Scenebuilder scene for stitching video clips together. Use this tool to combine multiple clips into a unified scene.

Instructions

Create a new Scenebuilder scene for stitching clips. FREE. Flow's chat agent cannot do this — it is a UI-only surface.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "flow_create_scene"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A3.9/5.0

Behavior2/5

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

Annotations provide readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds only 'FREE' which is minor. It does not disclose side effects, return values, or any behavioral details beyond the annotations, leaving the agent without important context about state changes.

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?

The description consists of two short sentences that pack purpose and a key usage note with no fluff. Every sentence adds value, achieving maximum conciseness.

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

Completeness3/5

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

Given zero parameters and no output schema, the description is minimally adequate. It lacks information about what the tool returns (e.g., scene ID) or what 'Scenebuilder scene' means, which could leave an agent uncertain about how to use the result.

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?

The input schema has zero parameters, so schema description coverage is 100%. Baseline is 4 per guidelines. The description adds nothing about parameters, but there are none to describe.

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 uses a specific verb 'Create' and resource 'Scenebuilder scene' with purpose 'for stitching clips'. The sibling tools include other scene-related actions like flow_export_scene and flow_add_clips_to_scene, making this tool's purpose distinct.

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 statement 'Flow's chat agent cannot do this — it is a UI-only surface' provides clear context that this tool is the only way to create scenes programmatically, giving a strong when-to-use indication. It lacks explicit when-not or alternative tool comparisons, but the context is valuable.

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