Retrieve available video and image models, aspect ratios, and durations from Google Flow's UI or cache. Run once per session before generating to confirm supported options.
List video/image models, ratios, durations from Flow UI (live) or cache. Call once per session before generating.
| Name | Required | Description | Default |
|---|---|---|---|
| refresh | No | Force re-discovery from the open UI instead of cache. |
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the live-vs-cache duality and the once-per-session constraint, but omits whether a connected/open Flow UI is required, what the call costs, and whether results are exhaustive. For a read-only discovery tool this is minimally adequate rather than rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short sentences, no filler. The resource list is front-loaded and the calling constraint follows immediately, so an agent can act after one read.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a one-parameter listing tool with full schema coverage and no output schema, the description covers what is returned (models, ratios, durations) and when to call it. The remaining gap is the undeclared dependency on a live Flow UI session, which matters for a browser-driven tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100% and the single 'refresh' parameter is fully documented in the schema. The description's 'live or cache' phrasing mirrors that schema text rather than adding syntax or format detail, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ('List') and concrete resources (video/image models, ratios, durations), and scopes the source (Flow UI live or cache). It does not name a sibling explicitly, but 'before generating' clearly separates it from the flow_generate_* tools.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives explicit timing guidance: 'Call once per session before generating.' That is a clear when-to-use directive tied to the generate workflow, though it names no exclusions or alternatives (e.g., what to do if the cache is stale besides refresh).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.