google-slides-mcp

catalog_slides

Summarizes each slide's layout, elements, placeholders, and title to help select reusable template slides for new decks.

Instructions

Summarize each slide (layout, element makeup, placeholders, title). (1 call.)

Use after copy_presentation to choose which showcase example slide to reuse for each section of the new deck.

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

Input Schema

Name	Required	Description	Default
`presentation_id`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

A4.4/5.0

Behavior4/5

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

No annotations are provided, so the description must convey behavior. It indicates a read-like operation ('summarize') and notes it is one call, but doesn't explicitly state safety or idempotency. Still, it's sufficiently transparent for this type of tool.

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: first describes functionality, second gives usage context. No extraneous words, front-loaded with key information.

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

Completeness4/5

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

The description covers what the tool does and when to use it. It has an output schema, so return values are covered. Minor gap: no mention of prerequisites or limitations, but overall complete for a simple summarization tool.

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?

There is one parameter, presentation_id, with no description in the schema (0% coverage). The tool description does not elaborate on the parameter, but the parameter name is self-explanatory. Baseline for minimal additional value.

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 that the tool summarizes each slide with attributes like layout, element makeup, placeholders, and title. It also distinguishes itself by noting it is a single-call operation and suggests usage after copy_presentation.

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

Usage Guidelines5/5

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

The description explicitly says 'Use after copy_presentation to choose which showcase example slide to reuse for each section of the new deck,' providing clear when-to-use guidance and a specific context.

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