Skip to main content
Glama
AIWerk

@aiwerk/mcp-server-elevenlabs

by AIWerk

get_knowledge_base_list_route

Read-onlyIdempotent

List and filter ElevenLabs knowledge base documents by type, folder, creator, search term, or sort order, with pagination for browsing large collections.

Instructions

Get Knowledge Base List

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typesNoIf present, the endpoint will return only documents of the given types.
cursorNoUsed for fetching next page. Cursor is returned in the response.
searchNoIf specified, the endpoint returns only such knowledge base documents whose names start with this string.
sort_byNoThe field to sort the results by
page_sizeNoHow many documents to return at maximum. Can not exceed 100, defaults to 30.
folders_firstNoWhether folders should be returned first in the list of documents.
sort_directionNoThe direction to sort the results
parent_folder_idNoIf set, the endpoint will return only documents that are direct children of the given folder.
ancestor_folder_idNoIf set, the endpoint will return only documents that are descendants of the given folder.
created_by_user_idNoFilter documents by creator user ID. When set, only documents created by this user are returned. Takes precedence over show_only_owned_documents. Use '@me' to refer to the authenticated user.
show_only_owned_documentsNoIf set to true, the endpoint will return only documents owned by you (and not shared from somebody else). Deprecated: use created_by_user_id instead.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

D1.9/5.0
Behavior1/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds zero behavioral context—no mention of pagination, result ordering, rate limits, or what the response contains. It is effectively missing.

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?

The description is a single terse phrase that is under-specified rather than concise. For an 11-parameter list endpoint with filtering, sorting, and pagination, this is far too minimal to be structurally adequate.

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?

Given the complexity (11 parameters, pagination, filtering) and no output schema, the description is completely inadequate. It omits any explanation of how to use the filters, how pagination works, or what the return shape looks like.

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 11 parameters are fully documented in the schema itself. The description provides no additional meaning, which meets the baseline of 3 for high schema coverage.

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 Knowledge Base List' is a tautology that simply restates the tool name and title without adding any distinguishing information. It does not clarify scope, filtering, or how it differs from other knowledge base list endpoints like get_agent_knowledge_base_summaries_route.

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 guidance on when to use this tool versus alternatives. It doesn't mention pagination, filtering, or any prerequisite context that would help an agent select it correctly.

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