Skip to main content
Glama
Sign In
Google Workspace (GWS) MCP Server

Google Workspace (GWS) MCP Server

by conorbronsdon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

slides_get

Read-only

Retrieve all slides, layouts, masters, and page elements from a Google Slides presentation by providing its presentation ID.

Instructions

Get a presentation's slides, layouts, masters, and page elements.

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

Input Schema

NameRequiredDescriptionDefault
presentationIdYesThe presentation ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.4.1

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is known. The description adds the scope of what is fetched (slides, layouts, masters, page elements), but it does not disclose return format, pagination, or any response limits. It adds some context beyond annotations without contradiction.

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?

One sentence, directly front-loaded with the action and resource, with no filler. Every word contributes to the meaning.

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?

Given a single required parameter, full schema coverage, and annotations indicating a read-only/open-world operation, the description covers the essential calling context. It stops short of describing the response structure, but that is a minor gap for a simple read operation.

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?

Schema description coverage is 100% and the sole parameter, presentationId, already has a clear schema description ('The presentation ID'). The tool description does not add further semantic detail, so the schema carries the burden.

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 names a specific verb ('Get'), a clear resource ('a presentation'), and enumerates the exact content scope ('slides, layouts, masters, and page elements'). This distinguishes it from siblings such as slides_pages_get and slides_batchUpdate without ambiguity.

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 description implies the tool is for retrieving full presentation structure, but it does not explicitly state when to prefer it over slides_pages_get or when not to use it. Usage context is implied by the resource scope rather than stated as guidance.

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

Deploy Server

Other Tools