Google Slides
Enable agents to create and edit Google Slides presentations. Build presentations programmatically with text, images, and formatting.
Available Tools
8 tools available in this integration
GoogleSlides.CommentOnPresentation Comment on a specific slide by its index in a Google Slides presentation
GoogleSlides.ListPresentationComments List all comments on the specified Google Slides presentation
GoogleSlides.CreatePresentation Create a new Google Slides presentation
GoogleSlides.CreateSlide Create a new slide at the end of the specified presentation
GoogleSlides.SearchPresentations Searches for presentations in the user's Google Drive
GoogleSlides.WhoAmI Get comprehensive user profile and Google Slides environment information
GoogleSlides.GenerateGoogleFilePickerUrl Generate a Google File Picker URL for user-driven file selection
GoogleSlides.GetPresentationAsMarkdown Get the specified Google Slides presentation and convert it to markdown
Why agent-optimized tools matter
Built for intent, not API schemas
Forcing the agent to juggle not only what you want to get done, but also how to operate all the APIs it needs to use is a recipe for disaster. Agent-optimized tools keep the agent focused on the work at hand, not ID hunting.
Up to 100x fewer tokens
Context bloat is a serious problem that gets in the way of real work getting done with agents. Agent-optimized tools return only the fields the agent needs to get the job done, not the full API response. Up to 100x less token consumption on every call.
Coverage for the whole task
Most tasks take more than one action to finish. Agent-optimized tools cover the full sequence so the agent completes the workflow end to end, not just the first lookup.
Consistent at scale
Agent-optimized tools behave the same across every user, every run, every harness, every model, and every effort level. No need for the agent to spend time and tokens re-learning the API shape, it can focus on the task at hand. What works for one user holds up when serving thousands in production.
Your questions, answered
It's built around what an agent is trying to accomplish rather than mirroring Google Slides's raw API. Fewer required parameters, far fewer tokens per call, and coverage for the whole task — so agents succeed more often.
Yes. The toolkit is exposed over an MCP gateway that any framework or MCP client can connect to, and we publish install guides for the editors and coding agents we document.
No. Arcade proxies API calls and does not persist your Google Slides content. Where Google Slides requires credentials, Arcade brokers them and stores them encrypted at rest — the model never sees them.
With Contextual Access policies: require human approval before consequential actions, redact sensitive fields on the way back, or restrict the scopes a given agent gets.
