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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_agent_conversation_ticket_route

Read-onlyIdempotent

Fetch an ElevenLabs agent conversation ticket by its ID to inspect conversation details for support or debugging.

Instructions

Get Agent Conversation Ticket

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": {
      "agentqa_ticket_id": "<agentqa_ticket_id>"
    },
    "name": "get_agent_conversation_ticket_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
agentqa_ticket_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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, covering the safety and idempotency profile. The description adds nothing beyond that, not even what a 'ticket' contains or whether the lookup can fail for a missing/foreign ID.

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?

It is a single short phrase, but the brevity comes from under-specification rather than efficiency. Nothing is front-loaded because nothing of substance is stated.

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 exists, so the description would need to say what is returned, and the lone parameter is undocumented. For a retrieval tool in a large sibling set, this leaves the agent without enough to invoke it confidently.

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?

The single parameter agentqa_ticket_id has 0% schema description coverage, and the description does not compensate at all — it never mentions the ID, its format, or where it comes from. With one undocumented param, the description should carry the burden and does not.

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 Agent Conversation Ticket' essentially restates the tool name and title without adding specificity. It names a verb and resource, but gives no clue how it differs from closely related siblings such as list_agent_conversation_tickets_route, get_conversation_history_route, or get_conversation_tag_route.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. An agent must infer from the name alone that this retrieves a single ticket by ID rather than listing them.

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