Skip to main content
Glama

get_recording

Retrieve the recording URL for a specific bot from the Attendee MCP Server to access meeting recordings.

Instructions

Get the recording URL for a bot

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bot_idYesID of the bot to get recording for

Implementation Reference

  • The handler function that retrieves the recording details for a bot by making an API request to /api/v1/bots/{bot_id}/recording and formats the response including URL, file size, and duration.
    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"),
          },
        ],
      };
    }
  • Input schema definition for the get_recording tool, specifying bot_id as required string parameter.
    inputSchema: {
      type: "object",
      properties: {
        bot_id: {
          type: "string",
          description: "ID of the bot to get recording for",
        },
      },
      required: ["bot_id"],
    },
  • src/index.ts:419-420 (registration)
    Switch case that registers and dispatches the get_recording tool call to the handler method.
    case "get_recording":
      return await this.getRecording(args);
  • src/index.ts:326-339 (registration)
    Tool registration in the listTools response, defining name, description, and input schema for get_recording.
    {
      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"],
      },
    },
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.

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/rexposadas/attendee-mcp'

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