Sign in Book a demo
Back to Tools
Productivity & Docs OAuth
Build Your Agent View Google Slides Docs
google-slides logo

Google Slides MCP Tools for AI Agents

Let an agent find decks, inspect slides, create presentations from templates, apply edits, and review or resolve comments.

Available Tools

10 tools available in this integration

GoogleSlides.CommentOnPresentation

Add a comment to a presentation, or reply within an existing comment thread.

GoogleSlides.CreateOrEditPresentation

Create a deck or apply a batch of edits to one, returning created object ids,

GoogleSlides.CreatePresentationFromTemplate

Derive a new on-brand deck from an existing branded deck, preserving its

GoogleSlides.GenerateGoogleFilePickerUrl

Generate a URL where the user grants this app access to specific Drive files.

GoogleSlides.GetPresentation

Return an addressable snapshot of a deck: slide and element object ids,

GoogleSlides.GetSlideThumbnail

Render one slide to a PNG.

GoogleSlides.ListPresentationComments

List a page of comments and their replies on a presentation, newest first.

GoogleSlides.ResolveComment

Close (resolve) or reopen a comment thread on a presentation.

GoogleSlides.SearchPresentations

Search the user's Drive for presentations, newest first by default.

GoogleSlides.WhoAmI

Return the connected Google account's profile (name, email, picture).

Why agent-optimized tools matter

Built for intent, not API schemas

Ask the agent to "find the latest quarterly review deck, update its title slide, and list the changed slides." Arcade helps it use the right Google Slides actions without guessing presentation, slide, or element IDs.

Up to 100x fewer tokens

Google Slides search and presentation reads return the deck structure and object IDs needed to act, while rendered PNGs are fetched only when visual review is needed. The agent avoids loading every slide image into its context.

Complete the workflow end to end

Search for a deck, inspect its structure, render a slide for review, apply edits, and manage feedback through one toolkit designed around the complete presentation task.

Make actions predictable and controlled

Arcade tools return structured results and useful errors across users and runs. Teams can apply scope restrictions, redaction, and approval policies so agents follow the same controls every time.

Securing Google Slides

The more capabilities agents get, the more useful they are. However, more capabilities bring more risks of undesired effects such as data loss and exfiltration.

This is why Arcade provides you with contextual rules that dictate how and when a tool is allowed to run. Arcade’s contextual access lets you govern tool visibility and behavior at every stage of execution and control who can see a tool, what inputs are allowed, and what comes back.

Learn about Contextual Access Policies

For Google Slides, you can implement some of these policies:

Access when tools are listed for a user
  • Hide GoogleSlides.CreateOrEditPresentation from agents unless the roles your IDP marks as presentation owners are active, so unapproved agents cannot overwrite or create decks.
  • Restrict GoogleSlides.CommentOnPresentation to agents operating under your designated communications roles, so drafts cannot publish comments to shared decks without the right audience.
  • Deny GoogleSlides.ResolveComment to everyone outside the roles your IDP marks as project leads, so agents cannot close open review threads without accountable ownership.
Pre-execution before each tool call
  • Require human approval before GoogleSlides.CreateOrEditPresentation runs, so an agent cannot alter an approved deck or create a new one without review.
  • Block GoogleSlides.CreatePresentationFromTemplate when the source deck is outside your approved template library, so an agent cannot generate branded work from an untrusted presentation.
  • Refuse GoogleSlides.CommentOnPresentation when the comment contains credentials, access tokens, or customer data, so an agent cannot publish secrets in a shared deck.
Post-execution after the tool returns
  • Redact slide text, hyperlinks, and embedded personal details from GoogleSlides.GetPresentation when the deck is marked confidential before the snapshot reaches the model.
  • Strip commenter email addresses and comment bodies from GoogleSlides.ListPresentationComments for decks under legal hold, so private review discussions do not reach the model.
  • Redact the connected user's email address and profile picture from GoogleSlides.WhoAmI before the agent receives account identity details.

How to use Google Slides with your agent

Pick your MCP client below and follow the setup end to end. Each user authorizes their own Google account before the agent can access their presentations.

Your questions, answered

A Google Slides MCP server exposes presentation capabilities as structured actions an AI agent can call through the Model Context Protocol. After a user authorizes Google, the agent can search presentations, inspect slides, create or edit decks, render slide previews, and manage comments.

Arcade provides the MCP connection and the Google Slides integration, so you do not have to build and maintain the OAuth, tool-calling, and permission flow yourself. It also adds user-level authorization, approval policies, redaction, and scope controls around presentation actions.

Arcade agents can search a user's presentations, inspect slide and element structure, render slide thumbnails, create decks, edit existing presentations, derive decks from branded templates, add or reply to comments, and resolve or reopen comment threads. Users can also grant access to specific Drive files through a file-picker flow.

Arcade requests the Google OAuth access needed by the actions you enable. Read-only workflows need access to view the relevant presentations, while creating or editing decks and managing comments require edit access; granting access to selected files can narrow what the agent reaches.

Yes. Each user authorizes their own Google account through OAuth, and presentation actions run under that user's approved access. The agent can reach only the presentations and permissions that user has granted.

Yes. Contextual Access policies can require human approval before consequential Google Slides actions, such as creating or editing a deck, adding a comment, or resolving a comment thread. The call proceeds only once the policy is satisfied.

Arcade proxies Google Slides and Drive API calls and does not persist your presentation content as part of normal tool execution. OAuth credentials are brokered and stored encrypted at rest, and the model never receives them.

Any framework or client that can connect to Arcade's MCP gateway or tool APIs works, including LangChain, OpenAI Agents, CrewAI, Claude Desktop, Claude Code, Cursor, Visual Studio Code, Microsoft Copilot Studio, and GitHub Copilot.

Arcade refreshes access while the user's Google authorization remains valid. If that authorization is revoked, rotated, or can no longer be refreshed, presentation actions stop until the user reconnects Google.

Google Slides and Drive API quotas, including per-user and project-level limits, apply to calls made through Arcade. Design agents to search narrowly and process presentations in reasonable batches rather than assuming unlimited API capacity.

Ready to actually ship your agent?

Connect your agent to Google Slides with managed OAuth, agent-optimized tools and approval controls for consequential actions.

Build Your Agent Read the Google Slides Quickstart