MCP server for Google Labs creative tooling — Veo video generation, image generation/editing and multimodal (Omni-style) reasoning through the Gemini API.
Three tools with clear names and reasonable descriptions, but critical gaps in schema completeness and parameter documentation. setup_status and list_models have minimal input schemas (empty/single param), while generate_video lacks critical safety parameters (duration, quality, model selection). Descriptions are adequate (60-150 chars) but lack actionable guidance on prerequisites, error recovery, and billing implications. No output schemas documented. Missing parameter descriptions for 'filter' in list_models. No error handling guidance visible in definitions.
STARTS a video generation with Veo (the model side of Flow/Omni). Generation takes time; this tool returns an operation name immediately and you fetch the result with check_video_operation. THIS IS BILLED — Veo charges per generation, so do not run batch generations without the user's approval.
Lists the Gemini/Veo/Imagen models this API key can actually reach. Use it when a model ID returns 404, or to find out which Veo version is available to the account.
Reports the installation status of the Google Labs integration: which API keys are set, which capabilities are active, and where the output folder is. Call this first when diagnosing setup problems.
generate_video lacks critical safety parameters: no duration limit, quality/resolution selector, or model override. Billing warning in description but no mechanism to prevent runaway generations. Missing output schema documentation.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., operation_id from generate_video, model_id from list_models). Violates pattern:tool requirement.
list_models 'filter' parameter has no description. LLMs cannot infer whether it accepts regex, substring match, or exact match. Violates pattern:tool-description.
generate_video description mentions billing but provides no recovery guidance if user declines. No confirmation/dry-run pattern. Agents cannot safely ask permission before executing.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 54 | 2026-07-28+ | v2 |
setup_status description lacks actionable error recovery. Does not explain what to do if keys are missing or partially set. Should reference SETUP_HELP or guide user to aistudio.google.com/apikey.