Skip to main content
Glama
Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Google Workspace MCP Server - Control Gmail, Calendar, Docs, Sheets, Slides, Chat, Forms & Drive

Create Presentation

create_presentation

Create a new Google Slides presentation and return its ID and URL for immediate use.

Instructions

Create a new Google Slides presentation and return its ID and URL.

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": {
      "user_google_email": "<user_google_email>"
    },
    "name": "create_presentation"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoThe title for the new presentation. Defaults to "Untitled Presentation".Untitled Presentation
user_google_emailYesThe user's Google email address. Required.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 readOnly=false, idempotent=false, openWorld=true, and destructive=false, so the safety profile is covered structurally. The description adds only that it returns an ID and URL — which the output schema already provides — and says nothing about where the file is created, auth requirements, or side effects of repeated calls (non-idempotent creation).

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 with no filler; verb, resource, and return value are all present. It is arguably too terse for a mutation tool, but nothing in it is wasteful.

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 an output schema present, the description needn't explain return values, and the tool is simple (two params, one required). However, for a non-idempotent create operation with no mention of destination location or authentication expectations, some behavioral context is still missing.

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 both the title (with its default) and the required user_google_email are fully documented in the schema. The description adds no semantics beyond that, which is acceptable at high coverage but earns only the baseline.

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+resource (create a new Google Slides presentation) and adds the return values (ID and URL), which distinguishes it from siblings like create_doc or create_spreadsheet by resource type. It does not explicitly contrast with batch_update_presentation or other presentation tools, but the resource name makes the target unambiguous.

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?

There is no guidance on when to prefer this over alternatives (create_doc, create_spreadsheet) or on prerequisites such as Google auth/scopes, aside from the required email parameter in the schema. Usage is implied by the verb but never stated or bounded.

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