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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

create_file_document_route

Create a file document for ElevenLabs agents from a local path or Base64 content, with optional custom name and parent folder placement.

Instructions

Create File Document

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

Input Schema

NameRequiredDescriptionDefault
nameNoA custom, human-readable name for the document.
file_pathNoDocumentation that the agent will have access to in order to interact with users. Local path. Required for this call.
file_base64NoBase64 contents for "file". Use this when the server cannot read your local disk.
file_filenameNoFilename to send for "file". Some endpoints infer the audio format from it.
parent_folder_idNoIf set, the created document or folder will be placed inside the given folder.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.1/5.0
Behavior2/5

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

The annotations (readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false) already convey that this is a non-idempotent write in an open world. The description adds no behavioral context beyond that – no mention of whether the base64/path inputs are mutually exclusive, what errors occur on failure, or what is created.

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?

Three words with zero waste, but this is under-specification rather than conciseness. The description is front-loaded only in the trivial sense that there is nothing behind it.

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

Completeness1/5

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

For a creation route that accepts either a local path or base64 content, with no required parameters and no output schema, the description supplies none of the disambiguation an agent needs. It is indistinguishable in intent from several sibling create_*_document_route tools.

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%, so all five parameters (name, file_path, file_base64, file_filename, parent_folder_id) are already documented in the schema. The description contributes nothing extra about them, so the baseline 3 for full schema coverage applies.

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?

"Create File Document" only restates the tool name/title with no additional specification. It gives a verb and a resource but nothing that separates it from siblings like create_text_document_route, create_url_document_route, or create_folder_route, which all create documents in the same workspace.

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 prerequisite, and no mention of the sibling routes an agent should choose between. The only signal about selection comes from the name itself, leaving the agent to guess how a "file document" differs from a text or URL document.

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