Skip to main content
Glama

remove_meeting_bot

Remove a bot from a meeting by specifying its ID to manage automated meeting participants.

Instructions

Remove a bot from a meeting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bot_idYesID of the bot to remove

Implementation Reference

  • The handler function for remove_meeting_bot tool. Validates bot_id, makes a POST request to `/api/v1/bots/{bot_id}/leave` API endpoint, and returns a formatted success message with updated bot status.
    private async removeMeetingBot(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}/leave`, "POST", {});
    
      return {
        content: [
          {
            type: "text",
            text: `āœ… Successfully requested bot ${bot_id} to leave the meeting.\n\nšŸ“Š Updated Status:\n${this.formatBotStatus(data)}`,
          },
        ],
      };
    }
  • The tool schema registration in the list of tools, defining name, description, and input schema requiring 'bot_id'.
    {
      name: "remove_meeting_bot",
      description: "Remove a bot from a meeting",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot to remove",
          },
        },
        required: ["bot_id"],
      },
  • src/index.ts:407-408 (registration)
    The switch case registration that dispatches tool calls named 'remove_meeting_bot' to the removeMeetingBot handler method.
    case "remove_meeting_bot":
      return await this.removeMeetingBot(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 action ('Remove') but doesn't clarify if this is destructive, reversible, requires specific permissions, affects meeting functionality, or has side effects. For a mutation tool 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 zero wasted words. It's front-loaded with the core action and target, making it immediately understandable 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?

For a mutation tool with no annotations and no output schema, the description is incomplete. It lacks behavioral context (e.g., permanence, permissions), doesn't explain what happens after removal, and offers no guidance on usage relative to siblings. Given the complexity of modifying meeting state, this leaves significant gaps.

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 schema description coverage is 100%, with the single parameter 'bot_id' fully documented in the schema. The description doesn't add any parameter details beyond what the schema provides, such as format examples or contextual meaning. Baseline 3 is appropriate when the schema does all the work.

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 bot from a meeting'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from sibling tools like 'delete_bot_data' or explain how removal differs from deletion, 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 like 'delete_bot_data' or 'create_meeting_bot'. It doesn't mention prerequisites (e.g., bot must be in a meeting), exclusions, or contextual triggers, leaving the agent to infer usage from the name 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/rexposadas/attendee-mcp'

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