google-flow-mcp

Overview Schema Source Related Servers Discussions Admin

Upload a local image into Flow

flow_upload_media

Upload a local image file to use as a start frame or reference in a video generation project. Confirm the resulting media ID before animating.

Instructions

Upload a local image file into the Flow project so it can be used as a start frame or reference. Free. After upload, confirm the resulting media id with flow_list_media before animating it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file_path": "<file_path>"
    },
    "name": "flow_upload_media"
  }
}

Input Schema

Name	Required	Description	Default
`file_path`	Yes	Absolute path to a local image file

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 29, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations already indicate a mutation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds 'Free' and a post-upload step, but lacks details on file limits or overwrite behavior.

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?

Two sentences with the purpose front-loaded and no redundant words; every sentence adds value.

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?

For a simple upload tool with one parameter and no output schema, the description adequately covers purpose and next steps, though it omits potential constraints like file size or formats.

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?

The input schema has 100% coverage on the single parameter 'file_path' with a clear description. The tool description does not add further meaning 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 uploads a local image file into the Flow project for use as a start frame or reference, distinguishing it from sibling tools by mentioning confirmation with flow_list_media.

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 a usage step (confirm media id) and notes it is free, but does not explicitly state when to use this tool over alternatives or include when-not conditions.

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