Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

slides_manage_slide

Destructive

Delete, duplicate, or move a specific slide in a Google Slides presentation using its object ID or 1-based slide number.

Instructions

Delete, duplicate, or move a slide.

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>",
      "action": "<action>"
    },
    "name": "slides_manage_slide"
  }
}

Input Schema

NameRequiredDescriptionDefault
slideYesSlide objectId, or 1-based slide number
actionYes
toIndexNo0-based target for move
presentationIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is partly covered, but the description adds nothing about the three actions behaving differently: delete is irreversible, duplicate creates a new slide, move reorders. It also does not clarify that a single destructive flag conflates these or what happens to indices after deletion.

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?

One short, front-loaded sentence with no filler. It is efficient but so terse that the conciseness comes at the cost of operational detail rather than being a virtue.

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?

This is a multi-action mutation tool with four parameters, no output schema, and partial schema descriptions, so the description carries a substantial burden. It omits which parameters apply to which action, index semantics after delete/move, and any error or permission context.

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 coverage is 50%: slide and toIndex are documented in the schema, but presentationId is undocumented in both places. The description does not explain the action-to-parameter relationship, notably that toIndex is only meaningful for move and uses 0-based indexing while slide can be either an objectId or a 1-based number.

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 names a specific resource (a slide) and three concrete operations (delete, duplicate, move), so an agent can tell what the tool does without opening the schema. It does not explicitly distinguish itself from siblings such as slides_batch_update, which could plausibly perform similar edits.

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?

There is no guidance on when to use this tool versus slides_batch_update or slides_add_slides, and no per-action conditions. The description only enumerates the allowed actions already present in the action enum.

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