Skip to main content
Glama
Angad-2002

Attendee MCP Server

by Angad-2002

delete_bot_data

Remove all stored data for a specific bot, including recordings and transcripts, to manage privacy and storage.

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 executes the delete_bot_data tool by making a POST request to the API endpoint to delete all data associated with the specified bot and returns a confirmation 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 input schema definition for the delete_bot_data tool, specifying that it requires a 'bot_id' string 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:440-441 (registration)
    The switch case in the CallToolRequest handler that dispatches to the deleteBotData method when the tool name is 'delete_bot_data'.
    case "delete_bot_data":
      return await this.deleteBotData(args);
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 deletes data, implying it's destructive and irreversible, but lacks critical details: whether it requires specific permissions, if it's asynchronous or immediate, what happens on failure, or if there are rate limits. 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 key action ('Delete all data') and provides relevant examples ('recordings, transcripts, etc.') without unnecessary elaboration. Every word earns its place, 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 the tool's destructive nature, lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, irreversibility, or error handling, which are critical for safe use. The description alone is inadequate for a tool that permanently deletes data, leaving the agent with significant uncertainty.

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 the 'bot_id' parameter clearly documented. The description adds no additional parameter semantics beyond what the schema provides (e.g., it doesn't explain format or validation rules for bot_id). With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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'), with specific examples of what data is deleted ('recordings, transcripts, etc.'). It distinguishes from siblings like 'remove_meeting_bot' (which likely removes the bot itself rather than its data) and 'get_recording' (which reads rather than deletes). However, it doesn't explicitly contrast with all siblings, so it's not a perfect 5.

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., needing admin permissions), when-not-to-use scenarios (e.g., if data might be needed for compliance), or direct alternatives among siblings. The agent must infer usage from the tool name and context alone.

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

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