Skip to main content
Glama
Google Workspace MCP connector

Google Workspace MCP connector

by animesh-ex

slides_create

Create a Google Slides presentation from a title and slide definitions, including layouts, bullet points, two-column content, speaker notes, and images.

Instructions

Create a Google Slides presentation, optionally with slides (layout, title, bullets, two columns, speaker notes, images).

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
slidesNo
folderIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.1

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the write/external side-effect profile is covered. The description adds scope detail about what content can be created inline, but says nothing about required Drive/Slides authorization, what identifier or URL comes back, or how images are fetched from a public URL – gaps that matter for a creation tool with no output schema.

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?

A single front-loaded sentence naming the action first and the optional payload second, with no filler. It is dense but readable; the nested parenthetical is the only mild structural cost.

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?

With no output schema, the description should at least signal what the caller gets back (a presentation id or link) so the agent can chain into slides_add_slides or slides_set_text, and it leaves folderId unexplained. For a creation tool with three parameters and an open-world annotation, this is adequate but incomplete.

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 0%, so the description must compensate and partly does: it maps "bullets", "two columns", and "speaker notes" onto the body, body2, and notes fields. However, it never mentions folderId, and does not clarify the string-vs-array distinction for body or the meaning of the layout enum, leaving half the parameters' semantics to be guessed.

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 specific verb and resource ("Create a Google Slides presentation") and enumerates the optional slide content (layout, title, bullets, two columns, speaker notes, images), which lets an agent separate it from docs_create/sheets_create and from slides_add_slides. It stops short of explicitly naming the sibling it contrasts with, so it does not reach a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase "optionally with slides" implies this is the entry point for a brand-new deck, but there is no explicit when-to-use guidance, no statement about when to prefer slides_add_slides or slides_batch_update on an existing presentation, and no prerequisites. Usage is inferable rather than stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.