Skip to main content
Glama
Angad-2002

Attendee MCP Server

by Angad-2002
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

get_recording

Retrieve the recording URL for a specific meeting bot to access captured meeting content.

Instructions

Get the recording URL for a bot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bot_idYesID of the bot to get recording for

Implementation Reference

  • src/index.ts:655-702 (handler)
    The handler function `getRecording` that executes the tool logic: validates bot_id, calls the API to fetch recording data, formats file size and duration, and returns a formatted text response with the recording URL and metadata.
    private async getRecording(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}/recording`);

  const formatFileSize = (bytes?: number) => {
    if (!bytes) return "Unknown size";
    const sizes = ['B', 'KB', 'MB', 'GB'];
    const i = Math.floor(Math.log(bytes) / Math.log(1024));
    return Math.round(bytes / Math.pow(1024, i) * 100) / 100 + ' ' + sizes[i];
  };

  const formatDuration = (ms?: number) => {
    if (!ms) return "Unknown duration";
    const seconds = Math.floor(ms / 1000);
    const minutes = Math.floor(seconds / 60);
    const hours = Math.floor(minutes / 60);
    
    if (hours > 0) {
      return `${hours}h ${minutes % 60}m ${seconds % 60}s`;
    } else if (minutes > 0) {
      return `${minutes}m ${seconds % 60}s`;
    } else {
      return `${seconds}s`;
    }
  };

  return {
    content: [
      {
        type: "text",
        text: [
          `🎥 Recording for bot ${bot_id}:`,
          "",
          `📁 URL: ${data.url}`,
          `📊 Size: ${formatFileSize(data.file_size)}`,
          `⏱️ Duration: ${formatDuration(data.duration_ms)}`,
          "",
          "💡 This is a short-lived URL that expires after a certain time.",
        ].join("\n"),
      },
    ],
  };
}
  • src/index.ts:335-348 (schema)
    The tool schema definition including name, description, and inputSchema specifying the required 'bot_id' parameter.
    {
  name: "get_recording",
  description: "Get the recording URL for a bot",
  inputSchema: {
    type: "object",
    properties: {
      bot_id: {
        type: "string",
        description: "ID of the bot to get recording for",
      },
    },
    required: ["bot_id"],
  },
},
  • src/index.ts:431-432 (registration)
    The registration/dispatch case in the CallToolRequestSchema handler that routes calls to the getRecording method.
    case "get_recording":
  return await this.getRecording(args);
  • src/index.ts:203-400 (registration)
    The ListToolsRequestSchema handler that registers the tool by including it in the list of available tools.
    this.server.setRequestHandler(ListToolsRequestSchema, async () => ({
  tools: [
    {
      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"],
      },
    },
    {
      name: "get_bot_status",
      description: "Get the current status of a meeting bot",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot to check",
          },
        },
        required: ["bot_id"],
      },
    },
    {
      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"],
      },
    },
    {
      name: "list_meeting_bots",
      description: "List all active meeting bots",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
    {
      name: "remove_meeting_bot",
      description: "Remove a bot from a meeting",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot to remove",
          },
        },
        required: ["bot_id"],
      },
    },
    {
      name: "make_bot_speak",
      description: "Make a bot speak text during a meeting using text-to-speech",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot that should speak",
          },
          text: {
            type: "string",
            description: "Text for the bot to speak",
          },
          voice_language_code: {
            type: "string",
            description: "Voice language code (optional, defaults to 'en-US')",
            default: "en-US",
          },
          voice_name: {
            type: "string",
            description: "Voice name (optional, defaults to 'en-US-Casual-K')",
            default: "en-US-Casual-K",
          },
        },
        required: ["bot_id", "text"],
      },
    },
    {
      name: "send_chat_message",
      description: "Send a chat message from the bot to the meeting",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot that should send the message",
          },
          message: {
            type: "string",
            description: "Message text to send",
          },
        },
        required: ["bot_id", "message"],
      },
    },
    {
      name: "get_chat_messages",
      description: "Get chat messages from the meeting",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot to get chat messages for",
          },
        },
        required: ["bot_id"],
      },
    },
    {
      name: "get_recording",
      description: "Get the recording URL for a bot",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot to get recording for",
          },
        },
        required: ["bot_id"],
      },
    },
    {
      name: "send_image_to_meeting",
      description: "Send an image to the meeting through the bot (Google Meet only)",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot that should display the image",
          },
          image_url: {
            type: "string",
            description: "HTTPS URL of the image to display",
          },
        },
        required: ["bot_id", "image_url"],
      },
    },
    {
      name: "send_video_to_meeting",
      description: "Send a video to the meeting through the bot (Google Meet only)",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot that should play the video",
          },
          video_url: {
            type: "string",
            description: "HTTPS URL of the MP4 video to play",
          },
        },
        required: ["bot_id", "video_url"],
      },
    },
    {
      name: "delete_bot_data",
      description: "Delete all data associated with a bot (recordings, transcripts, etc.)",
      inputSchema: {
        type: "object",
        properties: {
          bot_id: {
            type: "string",
            description: "ID of the bot to delete data for",
          },
        },
        required: ["bot_id"],
      },
    },
  ] satisfies Tool[],
}));

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
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 states the tool retrieves a URL but doesn't explain what the URL provides (e.g., audio/video format, accessibility), whether it requires specific permissions, or any rate limits. This leaves significant gaps for a tool that likely involves media access.

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, clear sentence with zero waste, front-loading the key action and resource. It's appropriately sized for a simple tool, making it easy to scan and understand 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 cover behavioral aspects like authentication needs or what the returned URL entails, which are crucial for a media retrieval tool. This leaves the agent with insufficient context to use the tool 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?

The input schema has 100% description coverage, fully documenting the 'bot_id' parameter. The description adds no additional meaning beyond the schema, such as format examples or constraints, so it meets the baseline for high schema coverage without enhancing parameter understanding.

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 ('Get') and resource ('recording URL for a bot'), making the purpose understandable. It doesn't explicitly differentiate from siblings like 'get_bot_status' or 'get_meeting_transcript', which might also retrieve bot-related information, so it lacks sibling distinction for a perfect score.

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 with a recording available) or compare to siblings like 'get_meeting_transcript' for related data, leaving usage context implied at best.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools