ElevenLabs

elevenlabs_delete_service_account_api_key

Delete Service Account Api Key. Delete an existing API key for a service account

Bulk support: accepts service_account_user_ids, api_key_ids for batched execution.

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": {
      "service_account_user_id": "<service_account_user_id>",
      "api_key_id": "<api_key_id>"
    },
    "name": "elevenlabs_delete_service_account_api_key"
  }
}

Input Schema

Name	Required	Description	Default
`account`	No
`api_key_id`	Yes
`api_key_ids`	No
`service_account_user_id`	Yes
`service_account_user_ids`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 21, 2026

TDQS

B3/5.0

Behavior1/5

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

Annotation Contradiction: the description says 'Delete', which is inherently destructive, while annotations declare destructiveHint=false. Additionally, the description does not disclose irreversibility, permission requirements, or side effects, leaving important behavioral details unaddressed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded, with the main action stated immediately. The bulk support sentence adds valuable information without padding. The first sentence is somewhat redundant with the tool name, but overall it is appropriately concise.

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?

The tool has 5 parameters, no output schema, and sparse annotations, yet the description only covers the core delete action and bulk support. It omits details about account scoping, required parameter relationships, irreversibility, and potential permission prerequisites, leaving significant contextual gaps.

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?

With schema description coverage at 0%, the description carries the burden of explaining parameters. It only clarifies that the plural fields service_account_user_ids and api_key_ids support bulk execution, but it leaves the required singular parameters and the 'account' field semantically unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Delete') and the resource ('an existing API key for a service account'), making the tool's purpose unambiguous. It also distinguishes itself from related sibling tools like create/edit/get service account API key tools by explicitly focusing on deletion.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description conveys when to use the tool via the deletion semantics and mentions bulk execution support, but it does not explicitly explain when not to use it or provide alternative tool recommendations. Usage context is implied rather than fully specified.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ElevenLabs tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.