Skip to main content
Glama
@runapi.ai/gemini-omni-mcp

@runapi.ai/gemini-omni-mcp

by runapi-ai

create_character

Creates a Gemini Omni character from a text description and portrait reference image, with optional body image and audio preset IDs, returning the operation result.

Instructions

Run a synchronous Gemini Omni operation on RunAPI (create character). Returns the operation result.

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": {
      "descriptions": "<descriptions>",
      "reference_image_url": "<reference_image_url>"
    },
    "name": "create_character"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNoRunAPI model slug for this model line.
audio_idsNoAudio preset IDs returned by create-audio. Declared type: array.
descriptionsYesCharacter appearance, identity, style, clothing, or personality description. Declared type: string.
character_nameNoCharacter display name. Declared type: string.
reference_image_urlYesPublic portrait reference image URL. Declared type: string.
body_reference_image_urlNoOptional public full-body reference image URL; reference_image_url must provide the portrait. Declared type: string.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv0.3.1
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +{}
    • changedInput schema / properties / audio_ids / description
      Previous value: -"Audio preset IDs returned by create-audio."New value: +"Audio preset IDs returned by create-audio. Declared type: array."
    • changedInput schema / properties / body_reference_image_url / description
      Previous value: -"Optional public full-body reference image URL; reference_image_url must provide the portrait."New value: +"Optional public full-body reference image URL; reference_image_url must provide the portrait. Declared type: string."
    • changedInput schema / properties / character_name / description
      Previous value: -"Character display name."New value: +"Character display name. Declared type: string."
    • removedInput schema / properties / character_name / maxLength
      Removed value: -210
    • changedInput schema / properties / descriptions / description
      Previous value: -"Character appearance, identity, style, clothing, or personality description."New value: +"Character appearance, identity, style, clothing, or personality description. Declared type: string."
    • removedInput schema / properties / descriptions / maxLength
      Removed value: -20000
    • removedInput schema / properties / model / enum
      Removed value: -[
      -  "gemini-omni-character"
      -]
    • changedInput schema / properties / reference_image_url / description
      Previous value: -"Public portrait reference image URL."New value: +"Public portrait reference image URL. Declared type: string."
  2. Changed2 schema fields changedv0.2.2
    • addedInput schema / properties / body_reference_image_url
      Added value: +{
      +  "description": "Optional public full-body reference image URL; reference_image_url must provide the portrait.",
      +  "type": "string"
      +}
    • changedInput schema / properties / reference_image_url / description
      Previous value: -"Public character reference image URL."New value: +"Public portrait reference image URL."
  3. Changed6 schema fields changedv0.2.1
    • addedInput schema / properties / audio_ids / description
      Added value: +"Audio preset IDs returned by create-audio."
    • addedInput schema / properties / character_name / description
      Added value: +"Character display name."
    • addedInput schema / properties / character_name / maxLength
      Added value: +210
    • addedInput schema / properties / descriptions / description
      Added value: +"Character appearance, identity, style, clothing, or personality description."
    • addedInput schema / properties / descriptions / maxLength
      Added value: +20000
    • addedInput schema / properties / reference_image_url / description
      Added value: +"Public character reference image URL."
  4. Changed8 schema fields changedv0.2.0
    • addedInput schema / properties / audio_ids
      Added value: +{
      +  "items": {},
      +  "type": "array"
      +}
    • addedInput schema / properties / character_name
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / descriptions / type
      Added value: +"string"
    • removedInput schema / properties / poll_interval_ms
      Removed value: -{
      -  "exclusiveMinimum": 0,
      -  "type": "integer"
      -}
    • addedInput schema / properties / reference_image_url / type
      Added value: +"string"
    • removedInput schema / properties / timeout_ms
      Removed value: -{
      -  "exclusiveMinimum": 0,
      -  "type": "integer"
      -}
    • removedInput schema / properties / wait
      Removed value: -{
      -  "default": true,
      -  "description": "Poll until the task reaches a terminal status.",
      -  "type": "boolean"
      -}
    • addedInput schema / required
      Added value: +[
      +  "descriptions",
      +  "reference_image_url"
      +]
  5. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It states the operation is synchronous and returns a result, which is useful, but it omits whether a character is persisted, whether reference images are consumed or stored, what errors or limits apply, and what side effects occur.

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?

Two short sentences with no filler, so it is appropriately sized. However, it front-loads opaque wrapper jargon ("Gemini Omni operation on RunAPI") rather than the actual action, which weakens front-loading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a six-parameter mutation tool with no annotations and no output schema. The description does not explain the required reference-image dependency, the role of audio_ids, or what the returned operation result contains, leaving significant gaps for an agent invoking it correctly.

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 description coverage is 100%, so all six parameters are already documented in the schema. The description adds no parameter-specific meaning beyond the schema, which makes the baseline score of 3 appropriate.

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

Purpose3/5

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

The parenthetical "(create character)" identifies the resource, but the main verb is a generic wrapper phrase: "Run a synchronous Gemini Omni operation on RunAPI." It distinguishes the tool from create_audio by name, but it does not clarify what creating a character actually produces or how it differs from other generation tools.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool, when not to, or which siblings to prefer. It does not mention prerequisites such as needing a portrait reference image, nor does it point to create_audio for related audio setup.

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