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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_signed_url_deprecated

Read-onlyIdempotent

Fetches a signed URL for an ElevenLabs agent conversation by agent ID, with optional branch or version. Deprecated; use the current endpoint.

Instructions

Get Signed Url Deprecated upstream.

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

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.1/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, so the safety profile is covered. The description's only addition is the 'Deprecated' marker, which is a genuinely useful signal, but it omits the replacement path, expiry behavior of the signed URL, or any auth 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?

It is a single short sentence with no padding, but its brevity comes from under-specification rather than economy: every meaningful word is already in the tool name. There is no front-loaded explanation of what the caller receives.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Six parameters, a required agent_id, environment/branch/version resolution, and a conversation-id side effect ('cannot be used again') go entirely unexplained, and there is no output schema to compensate. For a deprecated endpoint whose semantics an agent cannot infer, this is inadequate.

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% across all six parameters, so the schema fully documents agent_id, branch_id, version_id, environment, debug_events_request, and include_conversation_id. The description adds nothing further about these parameters, which matches the baseline of 3 when the schema does the work.

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 restates the tool name almost verbatim ("Get Signed Url Deprecated upstream") without saying what resource a signed URL is produced for or what 'upstream' means. It never distinguishes itself from siblings like get_conversation_signed_link, get_knowledge_base_source_file_url, or get_single_use_token. This is tautology rather than purpose.

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 statement of when to call this tool, when not to, or which alternative signed-URL/token tool to prefer. The word 'Deprecated' hints an agent should look elsewhere, but the description never names the replacement or the condition that selects this tool.

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