Skip to main content
Glama
Sign In
Docs Bridge

Docs Bridge

by dylansantwani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

slides_create

Create a Google Slides deck from scratch or a copied template and optionally add or edit slides in the same call.

Instructions

Create a Google Slides presentation, optionally from a template deck (any deck URL or id: it is copied), and optionally fill it with slides in the same call. For a new blank deck the first entry fills its existing title slide (give it a layout to change that), the rest are added after it.

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": {
      "title": "<title>"
    },
    "name": "slides_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleYes
slidesNoSlides to write, as in slides_write.
accountNoWhich signed-in Google account to use: an index as in /u/N/ URLs (0 = first account) or an email address. Omit for the browser default. Use this for presentations owned by a second (e.g. school) account.
templateNoA deck to copy as the starting point (URL or id).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and does disclose some non-obvious behavior: the template deck is copied rather than mutated, and entries run in order against evolving numbering. However, it omits mutation/permission implications, account/auth caveats, and any failure behavior for a write-capable tool.

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

Conciseness4/5

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

Two sentences, front-loaded with the core action, and every clause carries information. The second sentence is dense with nested conditions ('give it a layout to change that') but stays on topic.

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?

For a 4-parameter creation tool with a nested 11-property slide object, no annotations, and no output schema, the description covers the main creation and fill paths but omits what the call returns (e.g. the new deck's id/URL) and any limit or permission context, leaving chaining and error handling underspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75% and the schema already documents the nested slide entry fields in depth, so baseline is 3. The description adds real meaning beyond the schema: that the template accepts 'any deck URL or id' and is copied, and that on a blank deck the first entry targets the existing title slide while later entries are appended.

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 specific verb and resource ('Create a Google Slides presentation') and clarifies the two optional paths (template copy, inline slide fill). It distinguishes itself from slides_write implicitly through the fill semantics and from slides_copy by noting the source deck 'is copied', but it never names an alternative sibling explicitly.

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 explains how the slides entries behave once you call it, but never says when to use slides_create versus slides_copy (copying an existing deck) or slides_write (filling an existing deck). An agent must infer tool selection from the name alone.

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