Skip to main content
Glama

retell_list_knowledge_bases

Retrieve all available knowledge bases to manage AI agent information sources for voice and chat interactions.

Instructions

List all knowledge bases.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler logic for the retell_list_knowledge_bases tool. Dispatches to the generic retellRequest helper with the specific API endpoint /list-knowledge-bases using GET method.
    case "retell_list_knowledge_bases":
      return retellRequest("/list-knowledge-bases", "GET");
  • src/index.ts:922-929 (registration)
    MCP tool registration for retell_list_knowledge_bases, defining name, description, and input schema (no required parameters).
    {
      name: "retell_list_knowledge_bases",
      description: "List all knowledge bases.",
      inputSchema: {
        type: "object",
        properties: {}
      }
    },
  • Input schema definition for the tool, specifying an empty object (no input parameters required).
    inputSchema: {
      type: "object",
      properties: {}
    }
  • Core helper function that performs authenticated HTTP requests to the Retell API, handling headers, body, errors, and JSON responses. Used by all Retell tools including this one.
    async function retellRequest(
      endpoint: string,
      method: string = "GET",
      body?: Record<string, unknown>
    ): Promise<unknown> {
      const apiKey = getApiKey();
    
      const headers: Record<string, string> = {
        "Authorization": `Bearer ${apiKey}`,
        "Content-Type": "application/json",
      };
    
      const options: RequestInit = {
        method,
        headers,
      };
    
      if (body && method !== "GET") {
        options.body = JSON.stringify(body);
      }
    
      const response = await fetch(`${RETELL_API_BASE}${endpoint}`, options);
    
      if (!response.ok) {
        const errorText = await response.text();
        throw new Error(`Retell API error (${response.status}): ${errorText}`);
      }
    
      // Handle 204 No Content
      if (response.status === 204) {
        return { success: true };
      }
    
      return response.json();
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden. It states the tool lists knowledge bases but doesn't disclose behavioral traits like pagination, rate limits, authentication requirements, or what 'all' entails (e.g., active only, includes metadata). For a list operation with zero annotation coverage, this is inadequate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with no wasted words. It's front-loaded and directly states the tool's purpose without unnecessary elaboration.

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?

Given the tool's simplicity (0 parameters) but lack of annotations and output schema, the description is incomplete. It doesn't explain what the list returns (e.g., format, fields) or behavioral aspects like ordering or limits, which are important for a list operation.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so no parameter documentation is needed. The description doesn't add parameter details, which is appropriate given the empty schema, earning a baseline score of 4 for this dimension.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'List all knowledge bases' clearly states the action (list) and resource (knowledge bases). It distinguishes from siblings like retell_get_knowledge_base (singular) and retell_create_knowledge_base (creation), but doesn't explicitly mention scope or filtering compared to other list tools like retell_list_agents.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention prerequisites, context for listing knowledge bases, or when to choose this over other list tools (e.g., retell_list_agents).

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/itsanamune/retellsimp'

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