Google Sites MCP

Overview Schema Source Related Servers Discussions Admin

Embed a Google Drive file or calendar

gsites_add_drive_item

Embed Drive docs, slides, sheets, forms, charts, or calendars into Google Sites by searching and inserting the first result after the selected section.

Instructions

Embed a file from the user's Google Drive: kind = docs | slides | sheets | forms | charts | calendar. 'query' searches the Drive (for calendar it filters the user's calendars) and the FIRST result is inserted, so use a specific query. 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": {
      "kind": "<kind>",
      "query": "<query>"
    },
    "name": "gsites_add_drive_item"
  }
}

Input Schema

Name	Required	Description	Default
`kind`	Yes
`query`	Yes	Search text, e.g. the file name

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 declare readOnly=false, idempotent=false, openWorld=true; the description usefully explains why it is non-idempotent (search-first-result semantics), where content is inserted, and that the last section is preselected by default. It omits permission/auth requirements and what happens on a failed or ambiguous search.

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 and the kind list, followed by the operational caveat about first-result matching and insertion position. Slightly dense in the middle but every sentence carries information.

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?

A mutation tool with no output schema; the description never says what is returned (e.g. an embed identifier) or how to recover if the wrong file is inserted. Adequate for calling it, but incomplete for handling the result.

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 only 50% and the enum kind values are bare, so the description carries weight: it explains that 'query' searches Drive and, for calendar, filters the user's calendars, and clarifies the meaning of each kind. It adds meaningful semantics beyond the schema.

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 ('Embed a file from the user's Google Drive') and enumerates the supported kinds. It does not distinguish itself from close siblings like gsites_add_drive_file or gsites_add_embed, so an agent cannot tell from this text alone which embed tool 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 Guidelines3/5

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

Gives real usage guidance for one parameter ('the FIRST result is inserted, so use a specific query') and explains where content lands. It stops short of stating when to prefer this over gsites_add_drive_file or gsites_add_embed, and offers no when-not conditions.

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