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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_conversation_summary_route

Read-onlyIdempotent

Retrieve a summary of an ElevenLabs conversation by ID, with optional max_messages to control inline chat turns and flag omissions.

Instructions

Get Conversation Summary

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": {
      "conversation_id": "<conversation_id>"
    },
    "name": "get_conversation_summary_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_messagesNoMaximum number of chat message turns to include inline. When the conversation has more than this, the messages are omitted and messages_omitted is set.
conversation_idYesThe id of the conversation you're taking the action on.

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=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not say whether summaries are pre-generated or computed on demand, whether there is a cost/latency implication, or how the summary relates to the underlying messages.

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 single four-word phrase contains no waste, but it is under-specification rather than genuine conciseness. It is front-loaded only in the trivial sense of being the entire description.

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 and only a title-level phrase, an agent cannot tell what the summary contains, its format, or how max_messages truncation surfaces. For a read tool with two parameters the safety annotations cover part of the burden, but the description is still too thin to be complete.

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 conversation_id and max_messages (including the messages_omitted behavior) are already fully documented in the schema. Baseline 3 applies because the description contributes no additional parameter meaning.

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 is a verbatim restatement of the tool name ('get_conversation_summary_route' -> 'Get Conversation Summary') and adds no distinguishing detail. It does not differentiate this tool from close siblings such as get_conversation_history_route, get_conversation_histories_route, or run_conversation_analysis.

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 guidance on when to use this tool versus the many conversation-related siblings, nor any prerequisites or exclusions. The agent is left to infer usage entirely from the name.

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