@runapi.ai/gemini-omni-mcp

create_audio

Creates an audio preset from a specified voice identity and display name via RunAPI, returning the Gemini Omni operation result.

Instructions

Run a synchronous Gemini Omni operation on RunAPI (create audio). 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": {
      "audio_id": "<audio_id>",
      "name": "<name>"
    },
    "name": "create_audio"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Audio preset display name. Declared type: string.
`model`	No	RunAPI model slug for this model line.
`audio_id`	Yes	Voice identity used for the audio preset. Declared type: string.
`example_dialogue`	No	Example dialogue demonstrating the voice style. Declared type: string.
`voice_description`	No	Voice characteristics such as pitch, tone, or accent. Declared type: string.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedv0.3.1Oct 26, 2026

changedInput schema / additionalProperties
```
Previous value: -falseNew value: +{}
```

changedInput schema / properties / audio_id / description

Previous value: -"Voice identity used for the audio preset."New value: +"Voice identity used for the audio preset. Declared type: string."

changedInput schema / properties / example_dialogue / description

Previous value: -"Example dialogue demonstrating the voice style."New value: +"Example dialogue demonstrating the voice style. Declared type: string."

removedInput schema / properties / example_dialogue / maxLength
```
Removed value: -120
```
removedInput schema / properties / model / enum
```
Removed value: -[
-  "gemini-omni-audio"
-]
```

changedInput schema / properties / name / description

Previous value: -"Audio preset display name."New value: +"Audio preset display name. Declared type: string."

removedInput schema / properties / name / maxLength
```
Removed value: -210
```

changedInput schema / properties / voice_description / description

Previous value: -"Voice characteristics such as pitch, tone, or accent."New value: +"Voice characteristics such as pitch, tone, or accent. Declared type: string."

removedInput schema / properties / voice_description / maxLength
```
Removed value: -20000
```

Addedv0.2.1Aug 5, 2026
Removedv0.2.0Jul 22, 2026
First observedv0.1.0Jun 24, 2026

TDQS

C2.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses one useful trait ('synchronous', implying a blocking call) and that it returns an operation result, but says nothing about side effects, permissions, idempotency, or what actually gets created. For an unannotated creation tool this is a significant gap.

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 and the operation type front-loaded. Efficient, though the jargon phrase is low-value relative to a clearer statement of outcome.

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?

A 5-parameter creation tool with no annotations and no output schema needs the description to explain what is produced and what side effects occur. 'Returns the operation result' is vague, and the intended output (audio clip vs. preset) is left ambiguous.

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 the schema already documents all five parameters. The description adds no specific meaning about how audio_id, name, or voice_description interact beyond what the schema states, so baseline 3 applies.

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 description names a verb and resource ('create audio') but the schema parameters (audio_id, voice_description, example_dialogue) suggest a voice *preset* is being defined, not an audio clip. The phrase 'Run a synchronous Gemini Omni operation on RunAPI' is jargon that doesn't clarify the actual outcome. An agent could not confidently distinguish this from text_to_video or create_character.

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?

No indication of when to use this versus siblings like text_to_video or create_character, and no prerequisites stated. Only implicit usage through the name 'create_audio'.

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

Deploy Server