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

@aiwerk/mcp-server-elevenlabs

by AIWerk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

delete_knowledge_base_document

DestructiveIdempotent

Deletes a knowledge base document or folder. Use force to remove it even if agents depend on it, and to delete child items in non-empty folders.

Instructions

Delete Knowledge Base Document Or Folder

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

Input Schema

NameRequiredDescriptionDefault
forceNoIf set to true, the document or folder will be deleted regardless of whether it is used by any agents and it will be removed from the dependent agents. For non-empty folders, this will also delete all child documents and folders.
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.5/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, openWorldHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that — it does not mention the cascade behavior or the force override that determines whether dependent agents are affected.

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 a single front-loaded fragment with no wasted words, which is structurally efficient. But it is under-specified rather than truly concise — the brevity comes at the cost of any actionable context.

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?

This is a destructive, cascading delete with no output schema and no usage context in the description. Annotations and the schema cover safety and the force flag, but an agent gets no guidance on verifying the target or on when deletion is the right operation.

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 both documentation_id and force (including the cascade and dependent-agent semantics) are fully documented in the schema. The description only hints at folder scope via "Or Folder" and adds no syntax or format detail, so baseline 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?

The phrase names the verb (Delete) and the resource (Knowledge Base Document), and the addition of "Or Folder" signals a scope broader than the tool name implies. However, it is essentially a restatement of the tool name with no differentiation from siblings such as post_knowledge_base_bulk_delete_route or delete_rag_index.

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 mention of prerequisites, and no routing to alternatives. The folder-deletion capability appears only as an unexplained suffix, with no indication of when a folder vs. a document is the intended target.

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