Google Sites MCP

Overview Schema Source Related Servers Discussions Admin

Add a content layout block

gsites_add_layout

Insert ready-made Google Sites content blocks—image-caption, multi-column, and image grids—after the selected section, including caption placeholders for layout setup.

Instructions

Insert a ready-made content block (image(s) + caption placeholders). 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. Layouts: image_caption, two_columns, three_images, three_columns, two_columns_side_captions, four_columns.

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": {
      "layout": "<layout>"
    },
    "name": "gsites_add_layout"
  }
}

Input Schema

Name	Required	Description	Default
`layout`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already say this is a non-read-only, non-destructive, non-idempotent open-world write. The description adds genuinely useful behavior beyond that: content lands after the selected section, and the default selection causes append behavior. It doesn't mention whether repeated calls accumulate blocks or what happens on failure, but the key state dependency is disclosed.

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?

Front-loaded with the action, followed by placement semantics and then the layout list. It is tight overall, though the enumerated layouts duplicate the schema enum and could have been replaced with more useful semantic detail.

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 single-parameter mutation with no output schema, the description covers what is inserted, where it goes, the default selection state, and the reorder escape hatch. Minor gaps remain: no mention of what the tool returns or whether placeholders must be populated by subsequent calls.

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% and there is one parameter, so the description carries some burden. However, the layout list simply repeats the enum values verbatim without explaining what each layout actually contains or how placeholders should be filled afterwards, so it adds little meaning beyond structured data.

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?

Uses a specific verb and resource ('Insert a ready-made content block') and clarifies it is distinct from reordering operations by pointing to gsites_move_section. It does not, however, distinguish itself from the similarly named sibling gsites_add_block, leaving ambiguity about which to pick.

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?

Explains the insertion context (after the currently selected section), the default behavior (last section selected, so it appends), and names a follow-up tool for reordering. It gives good situational framing but no explicit 'use this when/avoid this when' guidance against gsites_add_block or gsites_add_image.

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