Skip to main content
Glama

Kubeez

list_gemini_omni_characters

Read-onlyIdempotent

Scope: generate:media. List the user's saved Gemini Omni characters (newest first). Each character is a bundle of (reference image, description, optional voice_id) backed by an opaque provider character_id that the model uses to render the same identity across multiple clips. USE WHEN: the user references a saved character ('use my Maya 'character', 'render the brand mascot') — pull the matching character_id from this list and pass it in character_ids when calling generate_media with a gemini-omni-video-* / gemini-omni-flash-* model. ALSO check this PROACTIVELY whenever the user wants the SAME person + voice across multiple video clips (a series, a recurring spokesperson, a marketing ad set): if no fitting character exists yet, offer to create one first via manage_library(kind='character', action='create', ...) so the identity is locked across the whole campaign. RETURNS: characters (each row has id [internal UUID], character_id [the value to pass to generate_media], character_name, image_url, description, voice_id, created_at). Each character_id consumes 1 of the 7 reference slots in generate_media.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_gemini_omni_characters"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint/idempotent/non-destructive, so safety is free; the description adds real value on top by describing the return row fields, the opaque provider `character_id` semantics, and the constraint that each `character_id` consumes 1 of 7 reference slots in `generate_media`. It stops short of stating whether the list is paginated, capped, or empty on first use, which are the remaining behavioral unknowns for a list tool.

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?

Front-loaded: scope and core action come first, then USE WHEN triggers, then the proactive rule, then RETURNS. Every section earns its place, though the all-caps emphasis and the long middle sentence about multi-clip series make it denser than necessary for a zero-parameter list call.

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?

An output schema exists, and the description still enumerates the return fields, so an agent knows exactly what to look for without a second lookup. What's missing is shape-of-list detail — count limits, ordering guarantees beyond 'newest first', and behavior when the library is empty — for a tool whose whole job is enumeration.

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 tool takes zero parameters (schema coverage 100%), so the baseline is 4, but the description's parameter discussion concerns `character_ids` on a different tool rather than anything the caller supplies here. Since this tool has no inputs to disambiguate, the description neither helps nor harms on this dimension.

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?

Opens with a specific verb and resource ('List the user's saved Gemini Omni characters') plus ordering information ('newest first'). It then defines what a character actually is ('a bundle of (reference image, description, optional voice_id) backed by an opaque provider character_id'), which distinguishes it from the sibling list_gemini_omni_voices and list_assets without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit trigger phrases ('use my Maya character', 'render the brand mascot') and names the exact downstream call and parameter (`generate_media` with `character_ids` on gemini-omni-video-*/gemini-omni-flash-* models). It also adds a proactive-usage rule and names the fallback path (`manage_library(kind='character', action='create', ...)`) when no matching character exists, so when-not-to-use-this-alone is covered.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources