@aiwerk/mcp-server-elevenlabs

add_turn_comment_route

Add a comment to a specific turn in an agent conversation ticket, marking what went wrong at that transcript turn for review and debugging.

Instructions

Add Turn Comment To 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>",
      "turn_index": "<turn_index>",
      "comment": "<comment>"
    },
    "name": "add_turn_comment_route"
  }
}

Input Schema

Name	Required	Description
`comment`	Yes	What went wrong at this turn.
`turn_index`	Yes	Zero-based index of the transcript turn this comment refers to.
`agentqa_ticket_id`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 13, 2026

TDQS

C2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, and destructiveHint=false. The description adds nothing beyond that profile—it does not explain whether comments are appended, whether duplicates are created on retry, or any 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?

The description is a single short phrase, but it is under-specified rather than concise. No sentence earns extra value because there is essentially only a restated title.

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?

For a non-idempotent mutation with three required parameters and no output schema, the description is inadequate. It omits when to use it, how it relates to the ticket lifecycle, and what the agentqa_ticket_id refers to.

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 coverage is 67%: comment and turn_index are described in the schema, but agentqa_ticket_id is undocumented. The description contributes no parameter meaning at all, so it fails to compensate for the gap and adds nothing over the structured fields.

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 'Add Turn Comment To Agent Conversation Ticket' is essentially a title-cased restatement of the tool name. It identifies the verb (add) and resource (turn comment on a conversation ticket) but provides no detail about what a turn comment is or how this differs from the sibling add_ticket_comment_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?

No guidance is given about when to use this tool versus alternatives such as add_ticket_comment_route or update_agent_conversation_ticket_route. 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