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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

search_groups

Read-onlyIdempotent

Search user groups by name through the ElevenLabs MCP server to locate a target group for membership or access management.

Instructions

Search User Groups

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": "search_groups"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the target group.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing about search behavior, matching semantics, pagination, or result limits, so it contributes no behavioral context beyond the title.

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 three words, front-loaded, and free of filler. It is highly concise, though its extreme brevity leaves the tool under-specified for an agent that must differentiate it from similar siblings.

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

Completeness3/5

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

For a simple one-parameter search tool with full schema coverage and rich annotations, the description covers the core purpose. However, it does not help the agent select this tool over sibling group-listing or member-listing tools, and it omits any search-specific context.

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%, and the single parameter 'name' is documented in the schema as 'Name of the target group.' The description adds no additional meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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?

States a specific verb (Search) and resource (User Groups), so the basic action is clear. However, it does not distinguish this tool from sibling tools like get_groups_endpoint or get_workspace_members, leaving selection ambiguity.

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?

Provides no when-to-use guidance, no conditions, and no alternatives. The agent is left to infer that this tool searches groups by name, but no explicit context or exclusions are offered.

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