google-slides-mcp

delete_objects

Remove slides or page elements by their ID to clean up Google Slides presentations.

Instructions

Delete slides or page elements by ID. (1 API call.)

Use to prune the original showcase example slides after duplicating the ones you want.

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>",
      "object_ids": "<object_ids>"
    },
    "name": "delete_objects"
  }
}

Input Schema

Name	Required	Description	Default
`presentation_id`	Yes
`object_ids`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It discloses '1 API call' efficiency and scope (slides or page elements), but lacks details on reversibility, permissions, or side effects. The name implies destruction, so it is minimally adequate.

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 sentences, front-loaded with purpose, followed by a specific usage note. Every word earns its place with no redundancy.

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?

Given output schema exists, return value explanation is optional. However, the description omits important behavioral context like permanence, error handling, or batch behavior. It provides a use case and API call count but remains basic for a deletion tool.

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 description must add meaning. It only says 'by ID,' which does not elaborate on presentation_id or object_ids format, constraints, or usage beyond what the schema already shows.

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?

Description clearly states it deletes slides or page elements by ID. Verb 'delete' and resource 'slides or page elements' are specific, and the tool distinguishes itself from siblings like duplicate_slide or park_slides by focusing on removal.

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

Usage Guidelines4/5

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

Provides explicit use case: 'prune the original showcase example slides after duplicating the ones you want.' This guides when to use it, though no explicit when-not or alternatives are given.

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