Skip to main content
Glama
ChatterBoxIO

ChatterBox MCP Server

by ChatterBoxIO

joinMeeting

Join Zoom, Google Meet, or Microsoft Teams meetings to capture transcripts and audio recordings for meeting analysis and documentation.

Instructions

Join a Zoom, Google Meet, or Microsoft Teams meeting using the provided meeting ID and password and capture transcript and audio recording

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYesThe online conference platform (zoom, googlemeet, or teams)
meetingIdYesThe ID of the Zoom ('###########') or Google Meet ('xxx-xxx-xxx') or Microsoft Teams ('##########') meeting
meetingPasswordNoThe password or the passcode for the Zoom or Google Meet or Microsoft Teams meeting (optional)
botNameYesThe name of the bot
webhookUrlNoURL to receive webhook events for meeting status (optional)

Implementation Reference

  • The handler function that implements the joinMeeting tool logic by making a POST request to the Chatterbox API to deploy a meeting bot and capture transcript/audio.
    async ({ platform, meetingId, meetingPassword, botName, webhookUrl }: {
      platform: string;
      meetingId: string;
      meetingPassword?: string;
      botName: string;
      webhookUrl?: string;
    }) => {
      try {
        const response = await fetch(
          `${CHATTERBOX_API_ENDPOINT}/join`,
          {
            method: 'POST',
            headers: {
              "Content-Type": "application/json",
              "Authorization": `Bearer ${CHATTERBOX_API_KEY}`
            },
            body: JSON.stringify({
              platform,
              meetingId,
              meetingPassword: meetingPassword || '',
              botName: botName || '',
              webhookUrl: webhookUrl || ''
            })
          }
        );
    
        const data = await response.json();
    
        return {
          content: [{ type: "text", text: `Meeting bot deployed. Session ID: ${data.sessionId}` }]
        };
      } catch (error) {
        return handleApiError(error, "joinMeeting");
      }
    }
  • Zod schema defining the input parameters for the joinMeeting tool.
    {
      platform: z.enum(["zoom", "googlemeet", "teams"]).describe("The online conference platform (zoom, googlemeet, or teams)"),
      meetingId: z.string().describe("The ID of the Zoom ('###########') or Google Meet ('xxx-xxx-xxx') or Microsoft Teams ('##########') meeting"),
      meetingPassword: z.string().optional().describe("The password or the passcode for the Zoom or Google Meet or Microsoft Teams meeting (optional)"),
      botName: z.string().describe("The name of the bot"),
      webhookUrl: z.string().optional().describe("URL to receive webhook events for meeting status (optional)"),
    },
  • src/index.ts:70-72 (registration)
    Registration of the joinMeeting tool with MCP server, including name, description, and reference to schema/handler.
    server.tool(
      "joinMeeting",
      "Join a Zoom, Google Meet, or Microsoft Teams meeting using the provided meeting ID and password and capture transcript and audio recording",
  • Helper function for handling API errors in tool handlers, specifically invoked in joinMeeting with context 'joinMeeting'.
    function handleApiError(error: unknown, context: string): ToolResponse {
        console.error(`Error in ${context}:`, error);
        
        if (error instanceof Error) {
            return {
                content: [{ type: "text", text: error.message }],
                isError: true,
                _meta: {
                    errorCode: "ERROR",
                    errorMessage: error.message
                }
            };
        }
        
        return {
            content: [{ type: "text", text: "Server error" }],
            isError: true,
            _meta: {
                errorCode: "ERROR",
                errorMessage: "Server error"
            }
        };
    }
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 joining and capturing data, but lacks critical details: whether this requires specific permissions or authentication, if it's a read-only or mutative operation (e.g., does joining affect meeting state?), rate limits, error handling (e.g., invalid IDs), or what happens post-capture (e.g., where recordings are stored). The description is insufficient for a tool with significant behavioral implications.

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, well-structured sentence that efficiently conveys the core functionality without unnecessary words. It is front-loaded with the primary action ('join') and key outcomes, making it easy to parse. Every part of the sentence contributes essential information.

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 complexity (joining meetings and capturing data), lack of annotations, and no output schema, the description is incomplete. It fails to address critical behavioral aspects like permissions, mutative effects, error scenarios, or output format (e.g., how transcripts/recordings are returned). For a tool with significant operational impact, this leaves too many gaps for effective agent use.

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, providing clear documentation for all 5 parameters. The description adds minimal value beyond the schema, only implicitly referencing 'meeting ID and password' without elaborating on their semantics or the optional 'webhookUrl' for status updates. Since the schema does the heavy lifting, the baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('join'), the resources affected ('Zoom, Google Meet, or Microsoft Teams meeting'), and the outcomes ('capture transcript and audio recording'). It distinguishes itself from sibling tools like 'getMeetingInfo' (which likely retrieves information) and 'summarizeMeeting' (which likely processes existing data) by focusing on active participation and data capture.

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 'getMeetingInfo' or 'summarizeMeeting'. It does not mention prerequisites (e.g., needing valid credentials or meeting access), exclusions (e.g., not for already-ended meetings), or contextual triggers (e.g., use when real-time transcription is needed).

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/ChatterBoxIO/chatterboxio-mcp-server'

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