Skip to main content
Glama
taylorwilsdon

Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

by taylorwilsdon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Get Presentation

get_presentation
Read-onlyIdempotent

Retrieve details of a Google Slides presentation, including slide content, speaker notes, and geometry. Use to inspect deck structure before editing.

Instructions

Get details about a Google Slides presentation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
presentation_idYesThe ID of the presentation to retrieve.
include_geometryNoAlso list each slide's elements with their placement - transform (translate, and scale/shear when not identity) and intrinsic size, in raw EMU. Set this when adding slides to an existing deck so new elements can match its established margins and content width. Defaults to False.
user_google_emailYesThe user's Google email address. Required.
include_speaker_notesNoAlso report each slide's speaker (presenter) notes and the object ID of the shape holding them. Pass True when you need to read or edit notes: that shape ID is the only valid target for insertText/deleteText on notes, and batch_update_presentation writes notes by deleting the shape's existing text and inserting new text. Defaults to False.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.26.0
    • addedInput schema / properties / include_geometry
      Added value: +{
+  "default": false,
+  "description": "Also list each slide's elements with their\nplacement - transform (translate, and scale/shear when not identity)\nand intrinsic size, in raw EMU. Set this when adding slides to an\nexisting deck so new elements can match its established margins and\ncontent width. Defaults to False.",
+  "type": "boolean"
+}
  2. Changed1 schema field changedv1.24.0
    • addedInput schema / properties / include_speaker_notes
      Added value: +{
+  "default": false,
+  "description": "Also report each slide's speaker (presenter)\nnotes and the object ID of the shape holding them. Pass True when you\nneed to read or edit notes: that shape ID is the only valid target for\ninsertText/deleteText on notes, and batch_update_presentation writes\nnotes by deleting the shape's existing text and inserting new text.\nDefaults to False.",
+  "type": "boolean"
+}
  3. Addedv1.0.1

TDQS

A3.5/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety and side-effect profile is well covered. The description itself adds no further behavioral context, such as what the response contains, how optional include_* flags alter behavior, or auth requirements.

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?

The description is a single, direct sentence with no filler or redundant restatement of the title. It is appropriately sized for a simple retrieval tool, leaving detailed behavior to the schema and annotations.

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

Completeness5/5

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

Given the rich annotations, complete schema descriptions, and the presence of an output schema, nothing essential is missing for an agent to call this tool correctly. The optional parameter behaviors are thoroughly explained in the schema, so the tool definition as a whole is complete.

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%, so the baseline is 3 and the one-sentence tool description does not need to compensate for missing parameter documentation. The description itself adds no parameter-level meaning beyond what the input schema already provides.

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 states a concrete operation—get details about a Google Slides presentation—with a specific verb and resource type. It does not explicitly call out sibling tools, but the read-oriented verb and required presentation_id make its role clear versus creation/update tools.

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 about when to use this tool instead of create_presentation, batch_update_presentation, or other slides-related tools, and no exclusionary conditions are stated. The only usage signal is the verb 'get', which is implied rather than explicitly explained.

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