Skip to main content
Glama

send_image_to_meeting

Display images in Google Meet meetings using a bot to share visual content with participants.

Instructions

Send an image to the meeting through the bot (Google Meet only)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bot_idYesID of the bot that should display the image
image_urlYesHTTPS URL of the image to display

Implementation Reference

  • The main handler function that validates the bot_id and image_url parameters, makes an API request to send the image to the meeting via /api/v1/bots/{bot_id}/output_image, and returns a formatted success response.
    private async sendImageToMeeting(args: Record<string, unknown>) {
      const bot_id = args.bot_id as string;
      const image_url = args.image_url as string;
      
      if (!bot_id || typeof bot_id !== 'string') {
        throw new Error("Missing or invalid required parameter: bot_id");
      }
      
      if (!image_url || typeof image_url !== 'string') {
        throw new Error("Missing or invalid required parameter: image_url");
      }
    
      if (!image_url.startsWith('https://')) {
        throw new Error("Image URL must start with https://");
      }
      
      await this.makeApiRequest(`/api/v1/bots/${bot_id}/output_image`, "POST", {
        url: image_url
      });
    
      return {
        content: [
          {
            type: "text",
            text: `āœ… Image sent to meeting from bot ${bot_id}\nšŸ“· Image URL: ${image_url}\n\nšŸ’” The image should now be displayed in the meeting (Google Meet only)!`,
          },
        ],
      };
    }
  • Input schema defining the required parameters bot_id and image_url for the send_image_to_meeting tool.
    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"],
    },
  • src/index.ts:340-357 (registration)
    Tool registration in the ListTools response, including name, description, and input schema.
    {
      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"],
      },
    },
  • src/index.ts:422-423 (registration)
    Dispatch case in the CallToolRequestSchema handler that routes to the sendImageToMeeting method.
    case "send_image_to_meeting":
      return await this.sendImageToMeeting(args);
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. While it indicates this is a sending/display operation, it doesn't describe what happens to the image (is it displayed temporarily/permanently?), whether it requires specific bot permissions, what happens if the meeting isn't active, or any rate limits. For a tool that presumably interacts with live meetings, this leaves significant behavioral questions unanswered.

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 extremely concise - a single sentence that communicates the core functionality and key constraint. Every word earns its place with no redundant information or unnecessary elaboration. The structure is front-loaded with the main action and target.

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 this is a meeting interaction tool with no annotations and no output schema, the description is insufficiently complete. It doesn't explain what happens after sending (success/failure indicators), whether the image persists, how users see it, or any error conditions. For a tool that modifies meeting state, more behavioral context is needed despite the concise description.

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 fully documents both parameters (bot_id and image_url). The description doesn't add any additional parameter context beyond what's in the schema - it doesn't explain where to get bot_id values, what image formats are supported, or any constraints on image_url beyond HTTPS. This meets the baseline for high schema coverage.

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 an image') and target ('to the meeting through the bot'), with the specific platform constraint 'Google Meet only' providing useful context. However, it doesn't explicitly differentiate from sibling tools like 'send_video_to_meeting' or 'send_chat_message', which would require mentioning it's specifically for visual media display rather than text or video.

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 minimal guidance - it mentions 'Google Meet only' which sets a platform constraint, but offers no advice on when to use this tool versus alternatives like 'send_video_to_meeting' or 'send_chat_message', nor does it mention prerequisites (like needing a bot created first) or appropriate use cases for image sharing versus other communication methods.

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