Skip to main content
Glama
Angad-2002

Attendee MCP Server

by Angad-2002

list_meeting_bots

View active AI meeting bots that can join, record, transcribe, and participate in video conferences across platforms like Zoom, Google Meet, and Microsoft Teams.

Instructions

List all active meeting bots

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the list_meeting_bots tool. It fetches the list of bots from the API endpoint /api/v1/bots, handles different response formats, formats the output with status icons and truncated URLs, and returns a formatted text response.
    private async listMeetingBots() {
      const data = await this.makeApiRequest("/api/v1/bots");
    
      // Handle both array response and object with bots property
      const bots = Array.isArray(data) ? data : (data.bots || []);
    
      if (bots.length === 0) {
        return {
          content: [
            {
              type: "text",
              text: "📋 No active meeting bots found.",
            },
          ],
        };
      }
    
      const botList = bots
        .map((bot: any, index: number) => {
          const stateIcon = (bot.state === 'joining' || bot.state === 'joined' || bot.state === 'joined_recording') ? "✅" : "❌";
          const transcriptIcon = bot.transcription_state === 'complete' ? "✅" : "⏳";
          return `${index + 1}. Bot ID: ${bot.id}\n   📊 State: ${bot.state} ${stateIcon}\n   📝 Transcription: ${bot.transcription_state} ${transcriptIcon}\n   🔗 Meeting: ${bot.meeting_url.substring(0, 50)}...`;
        })
        .join("\n\n");
    
      return {
        content: [
          {
            type: "text",
            text: `📋 Active Meeting Bots (${bots.length}):\n\n${botList}`,
          },
        ],
      };
    }
  • src/index.ts:252-260 (registration)
    The tool registration in the ListToolsRequestSchema handler, defining the name, description, and empty input schema (no parameters required).
    {
      name: "list_meeting_bots",
      description: "List all active meeting bots",
      inputSchema: {
        type: "object",
        properties: {},
        required: [],
      },
    },
  • src/index.ts:416-417 (registration)
    The dispatch case in the CallToolRequestSchema handler that routes calls to list_meeting_bots to the listMeetingBots() method.
    case "list_meeting_bots":
      return await this.listMeetingBots();
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 ('List all active meeting bots') but doesn't describe what 'active' entails, whether it requires specific permissions, how results are formatted (e.g., list, pagination), or any rate limits. For a tool with zero annotation coverage, this leaves critical behavioral traits unspecified.

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 ('List all active meeting bots') with zero wasted words. It is front-loaded and directly conveys the core purpose without unnecessary elaboration, making it highly concise and well-structured for quick understanding.

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 complexity (listing active resources) and lack of annotations or output schema, the description is incomplete. It doesn't explain what 'active' means, what data is returned, or how to interpret results. For a tool with no structured fields to rely on, this leaves the agent with insufficient context to use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description doesn't add parameter details, but since there are no parameters, this is acceptable. Baseline is 4 for 0 parameters, as the description doesn't need to compensate for missing schema information.

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 'List all active meeting bots' clearly states the verb ('List') and resource ('active meeting bots'), making the purpose immediately understandable. It distinguishes from siblings like 'create_meeting_bot' or 'remove_meeting_bot' by focusing on listing rather than creation or deletion. However, it doesn't specify what 'active' means or how it differs from 'get_bot_status', which slightly reduces specificity.

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 an active meeting), exclusions (e.g., not for inactive bots), or comparisons to siblings like 'get_bot_status' or 'get_meeting_transcript'. The agent must infer usage from the name alone, which is insufficient for optimal tool selection.

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