Skip to main content
Glama
Angad-2002

Attendee MCP Server

by Angad-2002

send_video_to_meeting

Play MP4 videos in Google Meet meetings using a bot. Provide the bot ID and HTTPS video URL to display media during the meeting.

Instructions

Send a video to the meeting through the bot (Google Meet only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bot_idYesID of the bot that should play the video
video_urlYesHTTPS URL of the MP4 video to play

Implementation Reference

  • The handler function for send_video_to_meeting. It extracts bot_id and video_url from args, validates them (string, https://, ends with .mp4), makes a POST request to the API endpoint /api/v1/bots/{bot_id}/output_video with the video URL, and returns a formatted success message.
    private async sendVideoToMeeting(args: Record<string, unknown>) {
      const bot_id = args.bot_id as string;
      const video_url = args.video_url as string;
      
      if (!bot_id || typeof bot_id !== 'string') {
        throw new Error("Missing or invalid required parameter: bot_id");
      }
      
      if (!video_url || typeof video_url !== 'string') {
        throw new Error("Missing or invalid required parameter: video_url");
      }
    
      if (!video_url.startsWith('https://')) {
        throw new Error("Video URL must start with https://");
      }
    
      if (!video_url.endsWith('.mp4')) {
        throw new Error("Video URL must end with .mp4");
      }
      
      await this.makeApiRequest(`/api/v1/bots/${bot_id}/output_video`, "POST", {
        url: video_url
      });
    
      return {
        content: [
          {
            type: "text",
            text: `āœ… Video sent to meeting from bot ${bot_id}\nšŸŽ¬ Video URL: ${video_url}\n\nšŸ’” The video should now be playing in the meeting (Google Meet only)!`,
          },
        ],
      };
    }
  • The input schema defining parameters bot_id (string) and video_url (string, HTTPS MP4), both required.
    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"],
    },
  • src/index.ts:367-384 (registration)
    Tool registration in listTools response, including name, description, and input schema.
    {
      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"],
      },
    },
  • src/index.ts:437-438 (registration)
    Dispatcher case in CallToolRequest handler that routes to the sendVideoToMeeting method.
    case "send_video_to_meeting":
      return await this.sendVideoToMeeting(args);

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 mentions the platform constraint ('Google Meet only'), which is useful, but fails to describe critical behaviors like whether this action is reversible, what permissions are required, how the video is displayed, or any rate limits. For a mutation tool with zero annotation coverage, this leaves significant gaps.

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 front-loads the core action and includes the platform constraint concisely, making it easy 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 complexity of sending media in a meeting context, no annotations, and no output schema, the description is insufficient. It lacks details on behavioral outcomes, error conditions, or integration with sibling tools like 'create_meeting_bot'. For a tool that likely involves mutations and platform-specific constraints, more context is needed.

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?

Schema description coverage is 100%, so the schema already documents both parameters (bot_id and video_url) adequately. The description adds no additional semantic context beyond implying the video is played by the bot, which is already suggested by the parameter names. Baseline 3 is appropriate when the schema handles parameter documentation.

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 ('send a video') and target ('to the meeting'), specifying the resource (video) and platform constraint ('Google Meet only'). It distinguishes from siblings like 'send_image_to_meeting' by specifying video content, though it doesn't explicitly contrast with other media-sending tools.

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?

No guidance is provided on when to use this tool versus alternatives like 'send_image_to_meeting' or 'make_bot_speak', nor does it mention prerequisites such as needing a bot created via 'create_meeting_bot'. The description only states the basic function without context for selection.

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