gg-mcp

by tannht

Overview Schema Source Related Servers Discussions Admin

Python

Hybrid

delete_slide

Delete a slide from a Google Slides presentation by specifying its zero-based index.

Instructions

Delete a slide from a presentation by its 0-based index.

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": {
      "presentation_id": "<presentation_id>",
      "slide_index": "<slide_index>"
    },
    "name": "delete_slide"
  }
}

Input Schema

Name	Required	Description	Default
`presentation_id`	Yes
`slide_index`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.0Jun 23, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations provided, so description carries full burden. It does not disclose side effects like shifting of subsequent slide indices, error behavior for invalid index, or whether the operation is reversible.

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 clear, efficient sentence with no wasted words. However, it could be slightly expanded with minimal additional context without losing conciseness.

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

Completeness3/5

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

Adequate for a simple delete operation with two parameters. It covers the basic functionality but omits return type (no output schema), which is acceptable. Lacks error scenarios and safety notes.

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?

With 0% schema description coverage, the description adds meaning only for slide_index (0-based indexing) but not for presentation_id. It partially compensates but leaves significant gaps.

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 action (delete), the resource (slide from a presentation), and the method (by 0-based index). It effectively distinguishes from sibling tools like add_slide and add_text_to_slide.

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?

No guidance on when to use this tool versus alternatives, no prerequisites mentioned, no caution about index out-of-bounds or permission requirements.

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