Skip to main content
Glama

delete_bot_data

Remove all bot data including recordings and transcripts from the Attendee MCP Server to manage storage and privacy.

Instructions

Delete all data associated with a bot (recordings, transcripts, etc.)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bot_idYesID of the bot to delete data for

Implementation Reference

  • The handler function that implements the core logic for the 'delete_bot_data' tool. It validates the bot_id parameter, makes a POST request to the API endpoint `/api/v1/bots/${bot_id}/delete_data` to delete the bot's data, and returns a formatted success message.
    private async deleteBotData(args: Record<string, unknown>) {
      const bot_id = args.bot_id as string;
      
      if (!bot_id || typeof bot_id !== 'string') {
        throw new Error("Missing or invalid required parameter: bot_id");
      }
      
      const data = await this.makeApiRequest(`/api/v1/bots/${bot_id}/delete_data`, "POST");
    
      return {
        content: [
          {
            type: "text",
            text: [
              `✅ Successfully deleted all data for bot ${bot_id}`,
              "",
              "🗑️ The following data has been permanently deleted:",
              "• Recording files",
              "• Transcript data", 
              "• Chat messages",
              "• Participant information",
              "",
              "⚠️ This action cannot be undone.",
              "💡 Bot metadata is preserved for audit purposes.",
            ].join("\n"),
          },
        ],
      };
    }
  • The tool schema definition including name, description, and inputSchema specifying the required 'bot_id' parameter.
    {
      name: "delete_bot_data",
      description: "Delete all data associated with a bot (recordings, transcripts, etc.)",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot to delete data for",
          },
        },
        required: ["bot_id"],
      },
    },
  • src/index.ts:428-429 (registration)
    The switch case in the CallToolRequest handler that routes calls to 'delete_bot_data' to the deleteBotData method.
    case "delete_bot_data":
      return await this.deleteBotData(args);
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the destructive action ('Delete') but lacks critical details: whether deletion is permanent, requires specific permissions, has rate limits, or what happens on success/failure. For a destructive tool with zero annotation coverage, this is a significant gap in transparency.

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 that front-loads the core action ('Delete all data') and includes helpful examples ('recordings, transcripts, etc.'). There is zero wasted verbiage, making it highly concise and well-structured.

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 this is a destructive tool with no annotations and no output schema, the description is incomplete. It doesn't cover behavioral aspects like irreversibility, permissions, or response format, leaving the agent under-informed for a high-stakes operation. The description should compensate more for the lack of structured data.

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 'bot_id' fully documented in the schema. The description adds no additional parameter semantics beyond implying the bot_id identifies the target for deletion. This meets the baseline of 3 when the schema does the heavy lifting.

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 target ('all data associated with a bot'), including examples of what data is deleted ('recordings, transcripts, etc.'). It distinguishes from siblings like 'remove_meeting_bot' (which likely removes the bot itself) by focusing on data deletion. However, it doesn't explicitly contrast with siblings, preventing 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. It doesn't mention prerequisites (e.g., bot existence), exclusions (e.g., irreversible action), or comparisons to siblings like 'remove_meeting_bot'. This leaves the agent without context for tool selection.

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/rexposadas/attendee-mcp'

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