Skip to main content
Glama

ShareWatch

by ai.sharewatch
OverviewDiscussionsAdmin

Create Presentation

create_presentation

Create a new Google Slides presentation with optional slides.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesPresentation title
accountNoWhich connected Google account to create in, by its address, when the user has more than one — see get_status connections. Omit for the primary account.
slides_jsonNoJSON array of slide objects: [{"layout":"TITLE","title":"...","body":"..."}]. Layouts are Google Slides PredefinedLayout names — the same set build_presentation accepts: TITLE, TITLE_AND_BODY, TITLE_AND_TWO_COLUMNS, TITLE_ONLY, SECTION_HEADER, SECTION_TITLE_AND_DESCRIPTION, ONE_COLUMN_TEXT, CAPTION_ONLY, MAIN_POINT, BIG_NUMBER, BLANK. Unrecognised values are rejected before anything is created.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes
urlYes
accountNothe Google account the file was created in; present only when more than one is connected

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / account
      Added value: +{
+  "description": "Which connected Google account to create in, by its address, when the user has more than one — see get_status connections. Omit for the primary account.",
+  "type": "string"
+}
    • addedOutput schema / properties / account
      Added value: +{
+  "description": "the Google account the file was created in; present only when more than one is connected",
+  "type": "string"
+}
  2. Changed1 schema field changed
    • removedOutput schema / additionalProperties
      Removed value: -false
  3. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The description adds only that slides are optional; it says nothing about account side effects, what happens on duplicate titles, or whether the call creates an empty deck when slides_json is omitted.

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. It is arguably too terse for a mutation tool with three parameters, but there is no wasted text.

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?

An output schema exists, so return values are covered, and the schema documents all parameters. The remaining gap is the missing relationship to build_presentation and update_presentation, which an agent needs to select correctly among these near-identical siblings.

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 coverage is 100% and each parameter is documented in the schema, including the layout enum list and the account-selection rule, so the description needn't carry that load. It adds only the word 'optional' for slides, giving no meaning beyond the schema - the baseline 3.

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 new Google Slides presentation') plus scope ('with optional slides'). It does not differentiate from the sibling build_presentation, and the only hint of a relationship lives in the slides_json schema field rather than the description itself.

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?

No when-to-use guidance, no prerequisites, and no routing between this tool and build_presentation, preview_slides, or update_presentation, all of which sound applicable to the same task. The agent must guess whether 'create' precedes or replaces 'build'.

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

All ShareWatch toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources