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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_conversation_signed_link

Read-onlyIdempotent

Generate a signed link to start a conversation with an ElevenLabs agent, specifying branch, version, or environment and optionally including a one-time conversation ID.

Instructions

Get Signed Url

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": {
      "agent_id": "<agent_id>"
    },
    "name": "get_conversation_signed_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
agent_idYesAgent id (agent_…) or speech engine external id (seng_), resolved to the same underlying resource.
branch_idNoThe ID of the branch to use
version_idNoThe ID of the version to use
environmentNoThe environment to use for resolving environment variables (e.g. 'production', 'staging'). Defaults to 'production'.
debug_events_requestNoWhether to enable debug events. Only available for users with editor access to the agent.
include_conversation_idNoWhether to include a conversation_id with the response. If included, the conversation_signature cannot be used again.

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, openWorldHint=true, and destructiveHint=false. The description adds no behavioral context such as authentication requirements, expiration of the signed link, or what the link grants access to. It does not contradict the annotations, but it contributes nothing beyond them.

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 phrase, but it is under-specified rather than appropriately concise. It does not front-load usable context, and it omits information an agent needs to invoke the tool correctly.

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?

Given six parameters, no output schema, and many sibling tools, the description is far too thin to orient an agent. The rich input schema and annotations cover safety and parameters, but the description itself explains neither the purpose nor the usage context of the signed link.

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 the six parameters are already well documented in the input schema. The description adds no extra meaning about agent_id, branch_id, version_id, environment, debug_events_request, or include_conversation_id, so the baseline for full schema coverage applies.

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 says only 'Get Signed Url', which is a vague restatement of part of the tool name. It does not specify that the URL is for a conversation/agent resource, nor does it distinguish this from related URL tools such as get_agent_link_route or get_signed_url_deprecated.

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?

There is no guidance about when to use this tool, what it returns, or which sibling tool to use instead. The description provides no context for selecting it over the many other GET routes in the sibling list.

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