Google Sites MCP

Overview Schema Source Related Servers Discussions Admin

Create a new blank Google Site

gsites_create_site

Creates a new unpublished Google Sites draft in your Drive using a title, sets its name, and returns the editor URL to begin building.

Instructions

Workflow: open the new-site page, start a blank site and set its name. Returns the editor URL. Creates a new draft site in the user's Drive (not published). Requires being signed in (see gsites_open).

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

Input Schema

Name	Required	Description	Default
`title`	Yes	Site name, e.g. 'My portfolio'

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 5, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already cover readOnly=false, destructive=false, openWorld=true, idempotent=false, but the description adds real context beyond them: the site is a draft, not published, it lands in the user's Drive, it returns the editor URL, and sign-in is required. It does not warn that repeated calls with the same title create additional duplicate sites, which is the notable non-idempotent risk.

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?

Three short sentences, front-loaded with the workflow then the side effects and the return value. Slightly implementation-leaning in 'open the new-site page, start a blank site', but every sentence contributes something an agent needs.

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?

With no output schema, the description correctly supplies the return value (editor URL) and the auth prerequisite, which is the main thing an agent could get wrong. Only the duplicate-creation/rate behavior of a non-idempotent create is left unaddressed.

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 the single 'title' parameter already carries a description and min/max length. The description only restates it as 'set its name', adding no constraint or format meaning beyond the schema, so the baseline 3 applies.

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: start a blank site, set its name, create a new draft in the user's Drive. The word 'new' implicitly separates it from gsites_open_site/gsites_open_page, but no sibling is named explicitly, so the differentiation is inferred rather than stated.

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?

Usage is implied by 'open the new-site page, start a blank site' and the prerequisite 'Requires being signed in (see gsites_open)' routes the agent to the auth/session tool. There is no explicit when-not guidance or statement of what to call instead once the site exists (e.g. gsites_open_site).

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