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

Fetch Google Slides presentation details, including slides, layouts, elements, styles, speaker notes, and geometry, to analyze or modify a deck.

Instructions

Get details about a Google Slides presentation.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rawNoReturn the complete Slides API Presentation resource as JSON (slides, layouts, masters, notes, every element and style) instead of the summary. Nothing is filtered, so it can be large; prefer get_page with raw=True for a single slide. Overrides the other flags.
include_stylesNoAlso list each slide's elements with text styling (see get_page). Defaults to False.
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. Changed2 schema fields changedv1.30.1
    • addedInput schema / properties / include_styles
      Added value: +{
+  "default": false,
+  "description": "Also list each slide's elements with text styling\n(see get_page). Defaults to False.",
+  "type": "boolean"
+}
    • addedInput schema / properties / raw
      Added value: +{
+  "default": false,
+  "description": "Return the complete Slides API Presentation resource as JSON\n(slides, layouts, masters, notes, every element and style) instead\nof the summary. Nothing is filtered, so it can be large; prefer\nget_page with raw=True for a single slide. Overrides the other flags.",
+  "type": "boolean"
+}
  2. 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"
+}
  3. 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"
+}
  4. Addedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context of its own — it does not mention that a summary is returned by default, that raw=True returns the full unfiltered resource, or anything about payload size.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single short sentence with no waste and a clear lead verb. However, its extreme brevity means important scoping information is absent rather than merely condensed, so it is minimal rather than optimally structured.

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?

An output schema exists and annotations cover the safety profile, and 100% schema coverage documents every flag, so the agent can still call the tool correctly. The description nevertheless omits the tool's default summary-vs-raw behavior and its relationship to get_page, leaving a modest gap for a six-parameter read tool with several output-shaping flags.

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 all six parameters (raw, include_styles, include_geometry, include_speaker_notes, presentation_id, user_google_email) are already fully documented in the schema, including cross-tool hints. The description adds nothing beyond the schema, which is the expected baseline 3.

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?

States a clear verb+resource: retrieving details of a Google Slides presentation. It does not differentiate itself from siblings such as get_page (single slide), create_presentation, or batch_update_presentation, leaving the agent to infer the boundary from context.

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?

The description gives no when-to-use guidance, no alternatives, and no prerequisites. Some routing hints exist (e.g. 'prefer get_page with raw=True for a single slide') but they live in the schema's parameter descriptions, not the tool description, so the description itself contributes nothing.

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