Skip to main content
Glama
Sign In
mcp-google

mcp-google

by Antonio-byte10
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Criar projeto no Flow

flow_projeto_criar

Creates a new project in Google Flow with a specified name, without using credits. Characters must be recreated within the new project before use.

Instructions

Cria um projeto novo no Google Flow com o nome dado (ex.: um por vídeo ou por série). Não gasta créditos. Atenção: personagens ficam no projeto em que foram criados; num projeto novo, crie-os de novo (flow_personagem_criar) antes de usá-los.

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": {
      "nome": "<nome>"
    },
    "name": "flow_projeto_criar"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomeYesNome único do projeto.
tornar_padraoNoSe true, vira o projeto usado quando 'projeto' não é informado.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.16.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true. The description adds real value beyond them: it says the call costs no credits and discloses the project-scoping side effect on characters. It still does not say what the call returns or how the new project is identified afterwards.

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 short sentences, front-loaded with the action, then the cost note, then the caveat. Every sentence carries information; only the example parenthetical is optional padding.

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?

No output schema exists, so a note on what is returned (e.g., the new project identifier needed for later calls) would be the missing piece. Otherwise the cost profile, prerequisite and scoping behavior are all covered for a two-parameter creation tool.

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% and both parameters (nome, tornar_padrao) are documented in the schema. The description only restates that the project takes the given name and says nothing about tornar_padrao or the name-uniqueness / 80-char constraint, so it adds little over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Cria um projeto novo no Google Flow com o nome dado") plus a concrete grouping example (one per video or series). The resource distinguishes it from list/character tools, though it never names a sibling it could be confused with.

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?

Gives the selection intent (a project per video or per series) and a concrete prerequisite: characters are project-scoped, so in a new project you must recreate them with flow_personagem_criar before use. Names that alternative explicitly, but gives no explicit when-not-to-use case.

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

Deploy Server

Other Tools