Skip to main content
Glama
Angad-2002

Attendee MCP Server

by Angad-2002

create_meeting_bot

Join online meetings automatically to record and transcribe conversations. Specify a meeting URL from Zoom, Google Meet, or Microsoft Teams to deploy a bot that captures audio and generates text transcripts.

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 handler function that executes the create_meeting_bot tool. It extracts parameters, validates meeting_url, calls the API to create the bot, and returns a formatted response.
    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),
          },
        ],
      };
    }
  • Input schema for the create_meeting_bot tool defining meeting_url as required string and bot_name as optional string.
    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)
    Tool registration in the ListToolsRequestHandler, 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:407-408 (registration)
    Dispatch registration in the CallToolRequestHandler switch statement that routes calls to the handler.
    case "create_meeting_bot":
      return await this.createMeetingBot(args);
  • Helper function to format the bot 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 provided, the description carries the full burden of behavioral disclosure. It mentions the bot will 'join a meeting and record/transcribe it', which implies a long-running, potentially resource-intensive operation, but lacks details on permissions needed, rate limits, whether the bot persists after the meeting, or how to access the recording/transcript afterward. This is inadequate for a tool that likely involves significant backend processing.

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 directly states the tool's function without unnecessary words. It's front-loaded with the core action ('create a bot') and purpose, making it easy to parse quickly.

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 creating a bot for meeting recording/transcription, no annotations, and no output schema, the description is insufficient. It doesn't explain what happens after creation (e.g., how to check status, access outputs, or manage the bot), leaving critical gaps for an agent to use this tool effectively in a workflow.

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 fully documents both parameters. The description adds no additional meaning beyond what's in the schema (e.g., it doesn't clarify format constraints for 'meeting_url' or usage context for 'bot_name'). Baseline 3 is appropriate as the schema handles parameter documentation.

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 tool's purpose with a specific verb ('create') and resource ('bot'), and specifies the bot's function ('join a meeting and record/transcribe it'). However, it doesn't explicitly differentiate from siblings like 'list_meeting_bots' or 'remove_meeting_bot' in terms of creation vs. management operations.

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., meeting must be active), exclusions (e.g., not for meetings already being recorded), or comparisons to siblings like 'get_meeting_transcript' or 'get_recording' for accessing results.

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