Skip to main content
Glama

retell_delete_knowledge_base_source

Remove a source from a knowledge base to manage content and maintain accuracy in Retell AI's agent platform.

Instructions

Remove a source from a knowledge base.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
knowledge_base_idYesThe knowledge base ID
source_idYesThe source ID to delete

Implementation Reference

  • The switch case handler within the executeTool function that destructures the input arguments and makes a DELETE request to the Retell API endpoint for deleting a knowledge base source.
    case "retell_delete_knowledge_base_source": {
      const { knowledge_base_id: kbId, source_id } = args;
      return retellRequest(`/delete-knowledge-base-source/${kbId}/${source_id}`, "DELETE");
    }
  • The tool definition in the tools array, including name, description, and input schema for validation.
    {
      name: "retell_delete_knowledge_base_source",
      description: "Remove a source from a knowledge base.",
      inputSchema: {
        type: "object",
        properties: {
          knowledge_base_id: {
            type: "string",
            description: "The knowledge base ID"
          },
          source_id: {
            type: "string",
            description: "The source ID to delete"
          }
        },
        required: ["knowledge_base_id", "source_id"]
      }
    },
  • src/index.ts:1283-1285 (registration)
    Registration of the tool listing handler that exposes the tools array containing this tool to MCP clients.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return { tools };
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool removes a source, implying a destructive mutation, but does not address critical aspects like permissions required, whether the deletion is permanent or reversible, error handling (e.g., if the source doesn't exist), or rate limits. This leaves significant gaps in understanding the tool's behavior.

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 that efficiently conveys the core action without unnecessary words. It is front-loaded with the essential information ('Remove a source from a knowledge base'), making it highly concise and well-structured for quick understanding.

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 complexity of a destructive operation with no annotations and no output schema, the description is insufficient. It lacks details on behavioral traits (e.g., permanence, errors), output format, or integration with sibling tools. For a mutation tool with zero annotation coverage, more context is needed to ensure safe and correct usage.

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?

The input schema has 100% description coverage, with clear parameter definitions ('knowledge_base_id' and 'source_id'), so the schema already provides full parameter semantics. The description does not add any additional meaning beyond what the schema specifies, such as format examples or contextual usage of the IDs, which aligns with the baseline score of 3 when schema coverage is high.

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 ('Remove') and target ('a source from a knowledge base'), which is specific and unambiguous. However, it does not explicitly differentiate from sibling tools like 'retell_delete_knowledge_base' (which deletes the entire knowledge base) or 'retell_add_knowledge_base_sources' (which adds sources), though the distinction is implied by the tool name.

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, such as when to delete a source versus the entire knowledge base, or prerequisites like ensuring the source exists. It lacks explicit context or exclusions, leaving usage unclear beyond the basic action.

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