Google Sites MCP

Overview Schema Source Related Servers Discussions Admin

Add an image carousel

gsites_add_carousel

Create an image carousel from local image files (2+ recommended) and insert it after the selected Google Sites section, appending at the end by default.

Instructions

Create an image carousel from local image files (2 or more recommended). New content goes after the currently selected section; by default the last section is selected first so content is appended at the end. Use gsites_move_section to reorder afterwards.

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": {
      "file_paths": "<file_paths>"
    },
    "name": "gsites_add_carousel"
  }
}

Input Schema

Name	Required	Description	Default
`file_paths`	Yes	Absolute paths of images

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare write, non-idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds genuinely non-schema context about where the new carousel lands relative to the selected section and the default selection fallback, though it says nothing about failure modes or later editability.

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

Conciseness5/5

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

Three tight sentences, zero filler, with the primary action first and the placement caveat and follow-up tool immediately after. Nothing is repeated from the schema or annotations.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation tool with annotations covering the safety profile, the description supplies the insertion semantics an agent needs to place content correctly. Minor gaps remain around error handling and whether an existing carousel can be amended, but nothing critical is 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% and the single file_paths parameter is documented as absolute paths with a 12-item cap. The description only adds the softer "2 or more recommended" hint, which is marginal beyond the schema's minItems/maxItems constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Create an image carousel") plus the source medium ("local image files"), which distinguishes it from siblings such as gsites_add_image and gsites_add_drive_item that pull content from elsewhere.

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

Usage Guidelines4/5

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

Gives clear situational guidance: at least two images recommended, content is inserted after the currently selected section, and gsites_move_section is named for reordering. It stops short of an explicit exclusion such as when to prefer gsites_add_image over a carousel.

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