Skip to main content
Glama

gflow_character_list

List the saved Flow CHARACTER entities in a project. Read-only, spends no credits. On flow.google.com, returns each character's entity_id, display_name, voice, personality, workflow_ids and thumbnail_media_id.

Instructions

List the saved Flow CHARACTER entities in a project. Read-only, spends no credits. On flow.google.com, returns each character's entity_id, display_name, voice, personality, workflow_ids and thumbnail_media_id. Pass entity_id in reference_entities paired with display_name in reference_entity_names (image and video r2v). On flow.google.com, an image @Name still attaches the first word after @ by name via the @ picker without reading the character catalog, while video @Name is not supported yet (exit 29, mention index unavailable); video r2v takes reference_entities plus reference_entity_names. Drives a browser.

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": {
      "project": "<project>"
    },
    "name": "gflow_character_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
profileNodefault
projectYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the safety burden itself and does so: "Read-only, spends no credits" plus "Drives a browser" tells the agent the cost and automation profile, and the exit-29 / "mention index unavailable" note discloses a real failure mode. It does not discuss auth requirements, rate limits, or what an empty project yields, which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is well front-loaded and the cost/read-only note early is good, but the middle passage chains three caveats about @ mention resolution, exit 29, and r2v reference pairs into a run-on that is hard to parse. Several clauses about @Name resolution are tangential to listing characters.

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?

An output schema exists, so enumerating entity_id/display_name/voice/personality/workflow_ids/thumbnail_media_id is redundant rather than harmful, and the browser-driving context is useful. The gap is on the input side: neither parameter is explained, and there is no statement of whether results are paginated or what happens for a project with no characters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the two parameters (project, profile), yet the description never explains what "project" identifies or what "profile" selects — it just repeats "in a project". Worse, most of the field talk (reference_entities, reference_entity_names) describes parameters belonging to sibling generation tools, not inputs to this one, so an agent gets no added meaning for the schema it must fill in.

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?

"List the saved Flow CHARACTER entities in a project" states a specific verb (list), a specific resource (CHARACTER entities), and a scope (per project), which cleanly separates it from gflow_character_show and gflow_character_voices without opening any schema.

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?

It gives concrete downstream guidance — "Pass entity_id in reference_entities paired with display_name in reference_entity_names (image and video r2v)" — and warns that image @Name attaches by name via the @ picker without reading the catalog, while video @Name is unsupported. What it never states is when to call this instead of the sibling gflow_character_show or gflow_character_voices, so it falls short of explicit alternative-routing.

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