Skip to main content
Glama
ChatterBoxIO

ChatterBox MCP Server

by ChatterBoxIO

getMeetingInfo

Retrieve meeting details including transcripts and recordings from Zoom or Google Meet sessions to generate summaries.

Instructions

Get information about a meeting

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sessionIdYesThe session ID to get information for

Implementation Reference

  • The handler function for the 'getMeetingInfo' tool. It makes an API request to retrieve session data, processes the transcript into a readable format, and returns structured information including recording link, timestamps, and transcript. Handles errors using handleApiError.
    async ({ sessionId }: { sessionId: string }) => {
      try {
        const response = await fetch(
          `${CHATTERBOX_API_ENDPOINT}/session/${sessionId}`,
          {
            headers: {
              "Content-Type": "application/json",
              "Authorization": `Bearer ${CHATTERBOX_API_KEY}`
            }
          }
        );
    
        const data = await response.json();
        if(data.message) {
          return {
            content: [{ type: "text", text: data.message }],
            isError: true,
            _meta: { errorCode: "ERROR", errorMessage: data.message }
          };
        }
    
        let transcript = "";
        if(data.transcript) {
          transcript = data.transcript.map((utterance: any) => 
            `${utterance.speaker}: ${utterance.text}`
          ).join('\n');
        } else {
          transcript = "No transcript data available";
        }
    
        return {
          content: [{ 
            type: "text", 
            text: JSON.stringify({
              recordingLink: data.recordingLink,
              startTime: data.startTimestamp,
              endTime: data.endTimestamp,
              transcript: transcript
            })
          }]
        };
      } catch (error) {
        return handleApiError(error, "getMeetingInfo");
      }
    }
  • Zod schema defining the input parameters for the 'getMeetingInfo' tool: requires a 'sessionId' string.
    {
      sessionId: z.string().describe("The session ID to get information for"),
    },
  • src/index.ts:117-168 (registration)
    Registration of the 'getMeetingInfo' tool using McpServer.tool(), specifying name, description, input schema, and inline handler function.
    server.tool(
      "getMeetingInfo",
      "Get information about a meeting",
      {
        sessionId: z.string().describe("The session ID to get information for"),
      },
      async ({ sessionId }: { sessionId: string }) => {
        try {
          const response = await fetch(
            `${CHATTERBOX_API_ENDPOINT}/session/${sessionId}`,
            {
              headers: {
                "Content-Type": "application/json",
                "Authorization": `Bearer ${CHATTERBOX_API_KEY}`
              }
            }
          );
    
          const data = await response.json();
          if(data.message) {
            return {
              content: [{ type: "text", text: data.message }],
              isError: true,
              _meta: { errorCode: "ERROR", errorMessage: data.message }
            };
          }
    
          let transcript = "";
          if(data.transcript) {
            transcript = data.transcript.map((utterance: any) => 
              `${utterance.speaker}: ${utterance.text}`
            ).join('\n');
          } else {
            transcript = "No transcript data available";
          }
    
          return {
            content: [{ 
              type: "text", 
              text: JSON.stringify({
                recordingLink: data.recordingLink,
                startTime: data.startTimestamp,
                endTime: data.endTimestamp,
                transcript: transcript
              })
            }]
          };
        } catch (error) {
          return handleApiError(error, "getMeetingInfo");
        }
      }
    );
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. 'Get information about a meeting' implies a read-only operation, but it doesn't specify what information is returned, whether it requires authentication, if there are rate limits, or any error conditions. This leaves significant gaps for an agent to understand the tool's behavior.

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 no wasted words. It's front-loaded with the core purpose, making it easy for an agent 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 lack of annotations and output schema, the description is incomplete. It doesn't explain what information is returned (e.g., meeting details, participants, timing), which is critical for a tool with 'get' functionality. The agent is left guessing about the tool's output and full behavior.

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 single parameter 'sessionId' documented as 'The session ID to get information for'. The description doesn't add any meaning beyond this, such as explaining what a session ID is or where to obtain it. With high schema coverage, 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.

Purpose3/5

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

The description 'Get information about a meeting' states a clear verb ('Get') and resource ('meeting'), but it's vague about what specific information is retrieved. It doesn't distinguish this tool from its sibling 'summarizeMeeting', which might also provide meeting information in a summarized form.

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 'summarizeMeeting' or 'joinMeeting'. It doesn't mention prerequisites (e.g., needing a sessionId) or contextual factors that would help an agent choose between these tools.

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