Skip to main content
Glama
Angad-2002

Attendee MCP Server

by Angad-2002

get_meeting_transcript

Retrieve transcribed text from recorded meetings using a bot ID. This tool extracts conversation content for documentation, analysis, or review purposes.

Instructions

Get the transcript from a meeting bot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bot_idYesID of the bot whose transcript to retrieve

Implementation Reference

  • The main handler function that executes the get_meeting_transcript tool. It validates the bot_id input, fetches the transcript via API, and formats the response using a helper.
    private async getMeetingTranscript(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}/transcript`);
    
      return {
        content: [
          {
            type: "text",
            text: this.formatTranscriptResponse(data, bot_id),
          },
        ],
      };
    }
  • The tool schema definition including name, description, and input schema (requires bot_id string). Registered in the ListTools handler.
    {
      name: "get_meeting_transcript",
      description: "Get the transcript from a meeting bot",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot whose transcript to retrieve",
          },
        },
        required: ["bot_id"],
      },
    },
  • src/index.ts:413-414 (registration)
    The switch case in the CallToolRequestHandler that routes calls to the getMeetingTranscript handler function.
    case "get_meeting_transcript":
      return await this.getMeetingTranscript(args);
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. It states the action ('Get') but doesn't clarify if this is a read-only operation, whether it requires specific permissions, what format the transcript returns (e.g., text, structured data), or any rate limits or errors. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior beyond the basic purpose.

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 ('Get the transcript from a meeting bot') that directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly. Every part of the sentence contributes to understanding the tool's core function.

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 (a data retrieval operation with no output schema and no annotations), the description is incomplete. It doesn't explain what the transcript contains (e.g., text, timestamps), how it's formatted, or any behavioral aspects like error handling. With no output schema to clarify return values, the description should provide more context to help the agent use the tool effectively, but it falls short.

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 'bot_id' clearly documented as 'ID of the bot whose transcript to retrieve'. The description doesn't add any meaning beyond this, such as how to obtain the bot ID or what happens if an invalid ID is provided. Given the high schema coverage, a baseline score of 3 is appropriate, as the schema adequately handles parameter semantics without extra description.

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 states the tool's purpose ('Get the transcript from a meeting bot'), which is clear but vague. It specifies the resource ('transcript') and implies the verb ('Get'), but doesn't differentiate it from sibling tools like 'get_chat_messages' or 'get_recording', which might retrieve related meeting data. The purpose is understandable but lacks specificity about what distinguishes this transcript retrieval from other data-fetching 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., needing a bot ID from 'list_meeting_bots'), exclusions, or comparisons to siblings like 'get_chat_messages' or 'get_recording'. Without any context on usage scenarios or alternatives, the agent must infer this from the tool name and schema 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/Angad-2002/attendee-mcp'

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