Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

slides_add_image

Places an image from a public URL on a Google Slides slide and sets its position and size in points.

Instructions

Place an image (public URL) on a slide. Position/size in points (deck is usually 720×405 pt).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "presentationId": "<presentationId>",
      "slide": "<slide>",
      "imageUrl": "<imageUrl>"
    },
    "name": "slides_add_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
xNo
yNo
slideYesSlide objectId, or 1-based slide number
widthNo
heightNo
imageUrlYes
presentationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior context beyond that — the image must be a public URL and geometry is in points on a ~720×405 pt deck — but says nothing about failure modes (unreachable URL, out-of-bounds coordinates), z-ordering, or whether existing content is displaced.

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?

Two short sentences, front-loaded with the action and immediately followed by the unit/scaling fact an agent needs to set coordinates correctly. No filler.

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?

For a 7-parameter mutation with no output schema, the description is thin: it never says what is returned (e.g., whether the created image's objectId is available for later repositioning) and leaves 6 of 7 parameters to a sparse schema. The unit and deck-size hints help, but not enough to make the definition self-sufficient for correct invocation.

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 only 14% (only `slide` is documented), so the description has to compensate and does so partially: it clarifies that imageUrl takes a public URL and that x/y/width/height are in points, plus the reference deck size that makes the 160/80/400/260 defaults interpretable. presentationId and the interplay of defaults vs explicit geometry remain unexplained.

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?

States a specific verb and resource ('Place an image ... on a slide'), which is enough to separate it from slides_add_text_box or slides_add_slides by artifact type. It stops short of naming or contrasting an alternative tool explicitly.

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

Usage Guidelines3/5

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

Usage is only implied: an agent knows to call this when it needs an image on an existing slide. There is no statement of prerequisites (does the slide need to exist, can it be a new slide, what happens on a duplicate) or of when to prefer batch_update for multi-element edits.

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