Skip to main content
Glama

create_meeting_bot

Create a bot to join video meetings and record or transcribe conversations. Automate meeting attendance for documentation purposes using Zoom, Google Meet, or Teams URLs.

Instructions

Create a bot to join a meeting and record/transcribe it

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meeting_urlYesURL of the meeting (Zoom, Google Meet, or Teams)
bot_nameNoName for the bot (optional, defaults to 'Go Bot')Go Bot

Implementation Reference

  • The main handler function for the 'create_meeting_bot' tool. It validates input parameters, makes a POST request to the API to create a meeting bot, and returns a formatted response using formatBotCreated.
    private async createMeetingBot(args: Record<string, unknown>) {
      const meeting_url = args.meeting_url as string;
      const bot_name = (args.bot_name as string) || "Claude Bot";
      
      if (!meeting_url || typeof meeting_url !== 'string') {
        throw new Error("Missing or invalid required parameter: meeting_url");
      }
    
      const data = await this.makeApiRequest("/api/v1/bots", "POST", {
        meeting_url,
        bot_name,
      });
    
      return {
        content: [
          {
            type: "text",
            text: this.formatBotCreated(data),
          },
        ],
      };
    }
  • The input schema definition for the 'create_meeting_bot' tool, specifying the expected parameters and validation rules.
    inputSchema: {
      type: "object",
      properties: {
        meeting_url: {
          type: "string",
          description: "URL of the meeting (Zoom, Google Meet, or Teams)",
        },
        bot_name: {
          type: "string",
          description: "Name for the bot (optional, defaults to 'Go Bot')",
          default: "Go Bot",
        },
      },
      required: ["meeting_url"],
    },
  • src/index.ts:205-223 (registration)
    The tool registration in the ListTools response, including name, description, and schema.
    {
      name: "create_meeting_bot",
      description: "Create a bot to join a meeting and record/transcribe it",
      inputSchema: {
        type: "object",
        properties: {
          meeting_url: {
            type: "string",
            description: "URL of the meeting (Zoom, Google Meet, or Teams)",
          },
          bot_name: {
            type: "string",
            description: "Name for the bot (optional, defaults to 'Go Bot')",
            default: "Go Bot",
          },
        },
        required: ["meeting_url"],
      },
    },
  • src/index.ts:398-399 (registration)
    The dispatch case in the CallToolRequest handler that routes to the createMeetingBot function.
    case "create_meeting_bot":
      return await this.createMeetingBot(args);
  • Helper function used by the handler to format the creation response.
    private formatBotCreated(data: any): string {
      return [
        "✅ Successfully created meeting bot!",
        "",
        `🤖 Bot ID: ${data.id}`,
        `🔗 Meeting URL: ${data.meeting_url}`,
        `📊 State: ${data.state}`,
        `📝 Transcription State: ${data.transcription_state}`,
        "",
        `💡 You can check the bot status using bot ID: ${data.id}`,
      ].join("\n");
    }
Behavior2/5

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

With no annotations, the description carries full burden but provides minimal behavioral context. It states the bot will 'join a meeting and record/transcribe it', implying mutation (creation) and data capture, but lacks details on permissions, rate limits, what happens if the bot fails, or whether recording is automatic. This is inadequate for a tool with potential side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/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. It avoids redundancy and wastes no words, though it could be slightly more structured (e.g., separating creation from functionality).

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 (creating a bot with recording/transcribing capabilities), no annotations, and no output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., bot ID, status), error conditions, or behavioral nuances, leaving significant gaps for an agent to use it effectively.

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%, so the schema already documents both parameters ('meeting_url' and 'bot_name') with descriptions. The description adds no additional meaning beyond implying the meeting_url must be for Zoom, Google Meet, or Teams (hinted in schema), resulting in a baseline score of 3.

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 ('create a bot') and its purpose ('to join a meeting and record/transcribe it'), specifying the resource (bot) and its function. It distinguishes from siblings like 'remove_meeting_bot' or 'get_meeting_transcript' by focusing on creation, but doesn't explicitly differentiate from other creation-related tools (none listed).

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?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., meeting access), exclusions, or compare to siblings like 'send_chat_message' for interaction. The description implies usage for recording/transcribing meetings but offers no contextual boundaries.

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