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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

list_image_generations

Read-onlyIdempotent

Retrieve image generations from ElevenLabs and filter them by status or model ID, with pagination for browsing results.

Instructions

List Image Generations

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_image_generations"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor: the `next_cursor` value of the previous page's response. Omit it for the first page.
statusNoOnly return generations with this lifecycle status.
model_idNoOnly return generations of this model.
page_sizeNoHow many generations to return per page.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, covering safety. The description adds nothing about pagination behavior, filtering semantics, or what 'Generations' encompasses. With annotations providing the safety profile, the description is purely tautological.

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?

The description is extremely short, but not in a helpful way – it's under-specified rather than concise. A single tautological phrase fails to earn its place.

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?

No output schema, and the description doesn't explain return values, pagination mechanics, or how to interpret the list. For a listing tool with four optional filters, more context about filtering and pagination would be expected.

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 four parameters (cursor, status, model_id, page_size) are fully documented in the schema. The description adds no parameter meaning, which is acceptable when schema coverage is high.

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 'List Image Generations' restates the tool name and title with no additional specificity. It does indicate a list operation on image generations, but doesn't distinguish from siblings like list_video_generations or list_text_to_speech_generations beyond the noun.

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

Usage Guidelines1/5

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

No guidance on when to use this tool versus alternatives. There are multiple listing tools for different asset types, and the description provides no routing hints.

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