Skip to main content
Glama

insert_slides_image

Insert an image from a public URL onto a Google Slide. Returns the image's object ID for repositioning, resizing, or deleting.

Instructions

Insert an image onto a slide from a publicly accessible URL.

Google Slides fetches the image from the URL at insert time and embeds a reference in the presentation. The URL must be publicly accessible (or accessible to Google's servers) at the moment of the call — private Drive URLs, signed URLs, and localhost URLs will fail. Supported formats: PNG, JPEG, GIF (Slides does not embed SVG).

Requires OAuth scope: https://www.googleapis.com/auth/presentations (write). Returns the new image's object ID so you can reference it later (reposition, resize, delete, etc.). Image size limit: 50 MB, 25 megapixels.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
user_google_emailYes
presentation_idYesGoogle Slides presentation ID (from the URL after `/d/`).
page_object_idYesObject ID of the slide to place the image on. Get it from `get_presentation.slides[].objectId`.
image_urlYesPublicly accessible HTTPS URL pointing to a PNG/JPEG/GIF. Google fetches this URL server-side; must return the image bytes directly (no login walls, redirects to interstitial pages, etc.).
leftNoX position (top-left corner) in EMUs (English Metric Units). Default `914400` EMU = 1 inch from the slide's left edge. Conversion: 1 inch = 914,400 EMU; 1 point = 12,700 EMU.
topNoY position (top-left corner) in EMUs. Default `914400` = 1 inch down.
widthNoImage width in EMUs. Default `3000000` ≈ 3.28 inches. Image is stretched/compressed to this size; aspect ratio is NOT preserved automatically — compute width:height from the source image to avoid distortion.
heightNoImage height in EMUs. Default `2000000` ≈ 2.19 inches.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Without annotations, the description fully discloses behavior: fetches image at insert time, embeds reference, requires public URL, formats, OAuth scope, return value, size limits, and EMU defaults. No contradictions.

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?

Concise paragraph with clear first sentence and structured details. Every sentence adds value with no redundancy or fluff.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters, no annotations, and an output schema (implied), the description covers behavior, constraints, return value, sizing, and defaults comprehensively.

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

Parameters5/5

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

Adds significant meaning beyond the schema: explains EMU conversions, default positioning, aspect ratio warning, and image size limits. Schema coverage is 88%, but description compensates for missing user_google_email description with other rich details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool inserts an image onto a slide from a URL, with specific verb and resource. It distinguishes from siblings like insert_doc_image (for Docs) and create_slides_shape (for shapes).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit instructions: URL must be publicly accessible, supported formats, OAuth scope required, returns object ID, and size limits. Tells when to use and when not (e.g., private URLs, SVG).

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/HuntsDesk/ve-gws'

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