Skip to main content
Glama

retell_delete_knowledge_base

Remove a knowledge base from the Retell AI platform by specifying its ID to manage agent information and resources.

Instructions

Delete a knowledge base.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
knowledge_base_idYesThe knowledge base ID to delete

Implementation Reference

  • Defines the Tool object for retell_delete_knowledge_base including name, description, and input schema requiring a knowledge_base_id.
    {
      name: "retell_delete_knowledge_base",
      description: "Delete a knowledge base.",
      inputSchema: {
        type: "object",
        properties: {
          knowledge_base_id: {
            type: "string",
            description: "The knowledge base ID to delete"
          }
        },
        required: ["knowledge_base_id"]
      }
    },
  • The switch case handler that executes the tool by calling retellRequest to DELETE the knowledge base via Retell API.
    case "retell_delete_knowledge_base":
      return retellRequest(`/delete-knowledge-base/${args.knowledge_base_id}`, "DELETE");
  • src/index.ts:1283-1285 (registration)
    Registers the listTools handler that returns the array of all tools, including retell_delete_knowledge_base.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
  • src/index.ts:1288-1293 (registration)
    Registers the callTool handler that dispatches to executeTool based on tool name, handling execution for retell_delete_knowledge_base.
    server.setRequestHandler(CallToolRequestSchema, async (request) => {
      const { name, arguments: args } = request.params;
    
      try {
        const result = await executeTool(name, args as Record<string, unknown>);
        return {
  • Generic helper function for making authenticated HTTP requests to the Retell API, used by the tool handler.
    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?

With no annotations provided, the description carries full burden but only states the action without behavioral details. It doesn't disclose if deletion is permanent, requires specific permissions, affects associated resources, or has rate limits. 'Delete' implies a destructive operation, but the description lacks crucial context for safe use.

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, direct sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse at a glance.

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?

For a destructive tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral risks, success/failure responses, or usage context. Given the complexity of deletion operations and lack of structured safety hints, more guidance is needed for reliable agent use.

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%, with the single parameter 'knowledge_base_id' fully documented in the schema. The description adds no additional parameter semantics beyond what's in the schema, so it meets the baseline score of 3 for high schema coverage without extra value.

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 clearly states the action ('Delete') and resource ('a knowledge base'), making the purpose immediately understandable. However, it doesn't differentiate this tool from sibling deletion tools like 'retell_delete_agent' or 'retell_delete_knowledge_base_source' beyond the resource name, which prevents a perfect score.

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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (e.g., whether the knowledge base must be empty), consequences, or relationships with sibling tools like 'retell_delete_knowledge_base_source' or 'retell_list_knowledge_bases' for verification.

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