Skip to main content
Glama
elevenlabs

ElevenLabs MCP Server

Official
by elevenlabs

add_knowledge_base_to_agent

Add a knowledge base document (epub, pdf, docx, txt, html) to an ElevenLabs agent to enhance its capabilities with specific information from a URL, file, or text input.

Instructions

Add a knowledge base to ElevenLabs workspace. Allowed types are epub, pdf, docx, txt, html.

⚠️ COST WARNING: This tool makes an API call to ElevenLabs which may incur costs. Only use when explicitly requested by the user.

Args:
    agent_id: ID of the agent to add the knowledge base to.
    knowledge_base_name: Name of the knowledge base.
    url: URL of the knowledge base.
    input_file_path: Path to the file to add to the knowledge base.
    text: Text to add to the knowledge base.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agent_idYes
knowledge_base_nameYes
urlNo
input_file_pathNo
textNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeYes
textYes
annotationsNo
_metaNo
Behavior4/5

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

Annotations already indicate non-destructive and open-world. Description adds cost warning and allowed file types, going beyond annotations.

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?

Description is clear and structured with a cost warning and parameter list. Slightly verbose due to Args, but effective overall.

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

Completeness4/5

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

Covers purpose, usage, parameters, and file types. With output schema present, return values need not be described. Missing details on how multiple sources interact, but still complete enough.

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

Parameters5/5

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

Schema coverage is 0%, but the Args section explains each parameter clearly (agent_id, knowledge_base_name, url, file, text), providing full meaning.

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?

Clearly states 'Add a knowledge base to ElevenLabs workspace' and specifies allowed file types. Distinguishes itself from sibling tools like create_agent or speech_to_text.

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

Usage Guidelines4/5

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

Includes a cost warning and explicit instruction to use only when user requests it. Does not mention when not to use or alternatives, but provides sufficient context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/elevenlabs/elevenlabs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server