Skip to main content
Glama
Sign In

ElevenLabs

by io.github.mcp-dir
OverviewDiscussionsAdmin

elevenlabs_search_groups

Read-onlyIdempotent

Search User Groups. Searches for user groups in the workspace. Multiple or no groups may be returned.

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

Input Schema

NameRequiredDescriptionDefault
nameYes
accountNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

Beyond the annotations (readOnlyHint, destructiveHint), the description adds that multiple or no groups may be returned, which is a useful behavioral detail. However, it does not mention parameter behavior, pagination, or any other traits like authentication or rate limits. Since annotations already declare safety, this additional context earns a modest score.

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

Conciseness3/5

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

The description is short but somewhat repetitive: 'Search User Groups' restates the tool name, and 'Searches for user groups in the workspace' repeats the same information. It is not as concise as it could be, but it is not overly verbose. The front-loaded purpose is clear, but the redundancy wastes a sentence.

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 two-parameter search tool with no output schema, the description is incomplete. It does not explain the parameters, which are essential for correct invocation, nor does it clarify the return format beyond saying multiple/none. The annotations help with safety, but the functional semantics are underspecified, leaving the agent guessing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema has two parameters (name and account) with zero description coverage. The tool description does not explain what these parameters are for; it only vaguely implies a search but never connects them to the parameters. This is a critical gap because the agent cannot infer that 'name' likely holds the search term or what 'account' controls.

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

Purpose4/5

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

The description clearly states that the tool searches for user groups in the workspace, using the verb 'search' and a specific resource. It also notes that multiple or no groups may be returned. However, it does not differentiate from a sibling tool like elevenlabs_get_groups_endpoint, so it lacks explicit distinction.

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 guidance on when to use this tool versus alternatives. The description simply states what it does without any context on when it is appropriate or preferable to other group-related tools. No exclusions or alternative tool mentions are given.

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

All ElevenLabs toolsInspect
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.

Resources