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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_knowledge_base_dependent_agents

Read-onlyIdempotent

List ElevenLabs agents that depend on a knowledge base document. Provide the document ID to filter by direct, transitive, or all dependencies.

Instructions

Get Dependent Agents List

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

Input Schema

NameRequiredDescriptionDefault
cursorNoUsed for fetching next page. Cursor is returned in the response.
page_sizeNoHow many documents to return at maximum. Can not exceed 100, defaults to 30.
dependent_typeNoType of dependent agents to return.
documentation_idYesThe id of a document from the knowledge base. This is returned on document addition.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.3/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 fully covered structurally. The description adds nothing beyond that — no note on pagination behavior, no scope of 'dependent' (direct vs transitive vs all), and no hint about what a dependent agent even is.

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?

It is maximally short and front-loaded, but the brevity comes from under-specification rather than efficient packing. Four words that only echo the title are less useful than a sentence that earns its place.

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 four-parameter retrieval tool with no output schema and multiple near-duplicate siblings, the description does not explain what dependent agents are, what the returned list contains, or how this differs from the bulk variant. It is too thin to guide correct invocation.

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% with four well-documented parameters (cursor, page_size, dependent_type enum, documentation_id), so the schema carries the semantics. The description contributes no additional parameter meaning, making the baseline 3 appropriate.

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 "Get Dependent Agents List" essentially restates the tool name (get_knowledge_base_dependent_agents) without adding a verb+resource specificity beyond it. It does not distinguish this tool from close siblings like get_knowledge_base_bulk_dependent_agents_route or get_tool_dependent_agents_route, so an agent cannot tell them apart from the text alone.

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 when-to-use guidance, no prerequisites, and no mention of alternatives. Given that sibling tools cover bulk dependent agents and tool dependent agents, the absence of any routing guidance leaves the agent to guess which retrieval is appropriate.

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