Google Sites MCP

by RXDG2908

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

Open a page of the open site by its name

gsites_open_page

Opens a page by exact name in a Google Sites editor via the Pages panel and returns its editor URL for direct editing.

Instructions

In the open site's editor, use the Pages panel (expanding collapsed groups) and open the page named exactly name. Returns the editor URL of that page.

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

Input Schema

Name	Required	Description	Default
`name`	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 only declare the generic safety profile (readOnly=false, destructive=false, openWorld=true, idempotent=false). The description adds real behavioral context: this drives the editor UI via the Pages panel, must expand collapsed groups, and returns the editor URL. It does not mention failure behavior when the name matches no page, which is a minor gap.

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?

Two compact sentences: the action and UI mechanism first, then the return value. No filler, and the exact-match constraint is placed right where it matters.

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 browser-automation tool with no output schema, the definition covers the prerequisite context, the matching rule, and the return value (editor URL). Missing only error conditions (page not found, collapsed group handling failures) that an agent might need to recover from.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single `name` parameter, so the description must carry the semantics — and it does, clarifying that the value is a page name requiring exact match rather than an ID, index, or path. It does not address case sensitivity or how group nesting affects the value.

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: open the page named exactly `name` in the open site's editor, and returns that page's editor URL. An agent can distinguish it from gsites_open_site / gsites_open, though those siblings are not named explicitly.

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 'In the open site's editor' implies a prerequisite (a site must already be open in the browser session), and 'Pages panel (expanding collapsed groups)' hints at the UI path. However, no explicit when-to-use/when-not guidance or named alternative (e.g., use gsites_open_site first, or gsites_set_page_title for renaming) is given.

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