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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_agents_route

Read-onlyIdempotent

Lists ElevenLabs agents by tag, name search, archived status, creator, sort order, and page size so you can browse or page through available agents.

Instructions

List Agents

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_agents_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsNoFilter agents by tag. Repeat the parameter to match any of several tags.
cursorNoUsed for fetching next page. Cursor is returned in the response.
searchNoSearch by agents name.
sort_byNoThe field to sort the results by
archivedNoFilter agents by archived status
page_sizeNoHow many Agents to return at maximum. Can not exceed 100, defaults to 30.
sort_directionNoThe direction to sort the results
created_by_user_idNoFilter agents by creator user ID. When set, only agents created by this user are returned. Takes precedence over show_only_owned_agents. Use '@me' to refer to the authenticated user.
show_only_owned_agentsNoIf set to true, the endpoint will omit any agents that were shared with you by someone else and include only the ones you own. Deprecated: use created_by_user_id instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered by structured data. The description adds nothing on top of that — no mention of pagination behavior, default page size, or that agents shared with you are included by default, which matters for a list endpoint with 9 optional filters.

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?

Two words are not concise, they are under-specified. Brevity here removes information rather than eliminating waste; a caller cannot act on the description alone.

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 9-parameter, zero-required list endpoint with no output schema, the description should at least touch on default result size, pagination via cursor, and default inclusion of shared agents. Annotations cover safety but not retrieval semantics, leaving the agent with the schema alone.

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 schema itself documents each filter, including the '@me' shortcut and the deprecation of show_only_owned_agents. The description contributes no additional parameter meaning, so the baseline of 3 applies.

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

Purpose3/5

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

"List Agents" states a verb and a resource, so the core operation is identifiable. However it gives no scope information (all vs. filtered, owned vs. shared, paginated) and does nothing to distinguish it from siblings like get_agent_summaries_route or get_tool_dependent_agents_route, despite the tool's rich filter set.

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 whatsoever on when to use this tool versus the many adjacent agent-retrieval tools, no prerequisites, and no mention of the archived/ownership filters that would shape a caller's choice.

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