Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

slides_add_slides

Add one or more slides to an existing presentation at the end or a chosen position, letting you build or extend Google Slides decks programmatically.

Instructions

Add one or more slides to an existing presentation (at the end or at a 0-based position).

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>",
      "slides": "<slides>"
    },
    "name": "slides_add_slides"
  }
}

Input Schema

NameRequiredDescriptionDefault
slidesYes
insertionIndexNo
presentationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare the additive, non-destructive, open-world profile, and the description is consistent with that by framing the operation as appending or inserting. It adds the 0-based indexing convention, which matters for correctness, but says nothing about what happens with an out-of-range index, whether previously existing slides shift, or what is returned (no output schema exists).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the key scoping and positioning information comes first. It is efficient but arguably too terse given the parameter detail it omits.

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 mutation tool with three parameters, 0% schema description coverage, and no output schema, the description does not do enough — nothing explains the slide payload structure or the effect of insertion on existing slides. An agent could invoke it, but would be guessing about the array-of-slide-objects semantics.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the load, and it only clarifies insertionIndex semantics. The slides array and its layout, body, body2, notes, title, and imageUrl fields are left entirely to the schema with no explanatory text in the description.

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: 'Add one or more slides to an existing presentation,' which clearly separates it from presentation creation (slides_create) and from slide-level edits. It doesn't name a sibling explicitly, so it stops short of a 5.

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?

The phrase 'at the end or at a 0-based position' implies when to supply insertionIndex versus omitting it, which is useful implicit routing. But there is no explicit guidance on when to use this versus slides_create, slides_batch_update, or slides_manage_slide, and no prerequisites are mentioned.

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