Google Sites MCP

Overview Schema Source Related Servers Discussions Admin

Add a YouTube video

gsites_add_youtube

Embed a YouTube video from a URL or search terms into Google Sites, placing it after the selected section so new content appends at the end.

Instructions

Embed a YouTube video from a URL or search words. 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": {
      "query": "<query>"
    },
    "name": "gsites_add_youtube"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	YouTube URL or search text

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 5, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=true, so the write/network profile is known. The description adds genuinely new behavior: where the block lands and how the default selection makes it append at the end. It does not say what happens when a search query matches multiple videos, which is the main unresolved behavior for an openWorld search-driven tool.

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 action, then placement, then the follow-up tool. The middle sentence ('by default the last section is selected first so content is appended at the end') is slightly circuitous but carries real information, so nothing is wasted.

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 insertion tool with annotations and no output schema, the description covers action, placement semantics, and a remediation path for ordering. The only real gap is ambiguity handling for search-word queries, which an agent would otherwise have to discover by calling it.

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?

There is one parameter with full schema description coverage ('YouTube URL or search text'), and the description restates the same URL-or-search-words duality without adding format, length, or query-resolution detail. With a 100% covered single parameter, the baseline of 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?

The description opens with a specific verb+resource: 'Embed a YouTube video from a URL or search words.' That distinguishes it from generic siblings like gsites_add_embed or gsites_add_drive_item, though it never names the near-duplicate gsites_add_embed explicitly as the alternative for non-YouTube embeds.

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?

It states the insertion context (after the currently selected section, defaulting to the last section) and names a concrete follow-up tool, gsites_move_section, for reordering. It stops short of saying when to prefer this over gsites_add_embed, but the placement guidance is clear enough to act on.

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