Skip to main content
Glama
Sign In
@aiwerk/mcp-server-elevenlabs

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_image_generation

Read-onlyIdempotent

Retrieve the status, details, and output of an ElevenLabs image generation by its ID to track progress and access the generated image.

Instructions

Get Image Generation

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": {
      "generation_id": "<generation_id>"
    },
    "name": "get_image_generation"
  }
}

Input Schema

NameRequiredDescriptionDefault
generation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered externally. The description adds nothing on top of that: no statement about what a lookup returns, failure behavior for an unknown id, or permission requirements.

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

Conciseness2/5

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

Three words is brief, but this is under-specification rather than conciseness: there is no front-loaded purpose statement that earns its place. The brevity costs the definition all useful information.

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?

With no output schema, one undocumented parameter, and a tautological description, an agent cannot know what the response contains or how the id is obtained. Annotations cover the safety profile but the descriptive burden for retrieval semantics is entirely unmet.

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 single required parameter generation_id, so the schema gives no meaning beyond the type. The description does not compensate at all, leaving the agent to guess that this is an identifier of an image generation resource.

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

Purpose2/5

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

The description "Get Image Generation" merely restates the tool name and title, adding no verb-resource specificity beyond what the identifier already conveys. An agent learns only that it retrieves something called an image generation, with no detail on scope or what is returned.

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?

There is no indication of when to use this tool versus siblings such as list_image_generations or create_image_generation, nor any prerequisites or exclusions. The sibling list makes the get/list/create distinction inferable, but the description itself provides nothing.

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