Google Sites MCP

Overview Schema Source Related Servers Discussions Admin

Add social media icon links

gsites_add_social_links

Adds a row of social media icons to a Google Sites section by turning each provided URL into an icon, then places it after the selected section for later reordering.

Instructions

Add a row of social icons. Each URL becomes one icon (Sites picks the icon from the domain: instagram.com, linkedin.com, github.com, youtube.com...). 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": {
      "urls": "<urls>"
    },
    "name": "gsites_add_social_links"
  }
}

Input Schema

Name	Required	Description	Default
`urls`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.0Nov 5, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare it is a non-destructive write with openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds genuinely useful behavior the annotations cannot: the icon is derived automatically from the URL's domain, and insertion position defaults to the last section. It omits the 8-icon cap and what happens for unrecognized domains.

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?

Three tight sentences ordered by importance: what is created, how inputs map to icons, where it lands, and how to fix placement. No filler, no repetition of the title, and the escape hatch is last where it belongs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A one-parameter, no-output-schema tool whose description covers creation semantics, input-to-output mapping, placement behavior, and follow-up reordering. The remaining gaps (item cap, unrecognized domains) are marginal for an agent deciding whether and how to call it.

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 description coverage is 0%, so the description must carry the load, and it does explain that each entry in `urls` produces exactly one icon with the icon chosen from the domain. It does not mention the minItems=1/maxItems=8 bounds or that entries must be full URIs, leaving the constraint side entirely to 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?

Specific verb and resource: "Add a row of social icons," with the one-URL-per-icon mapping spelled out. It distinguishes itself implicitly from the many other add_* siblings (add_button, add_embed, add_text) by naming the social-icon output, though it never explicitly contrasts itself with them.

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 model — new content lands after the currently selected section, with the last section selected by default — and routes the agent to gsites_move_section for reordering. It does not state when *not* to use this tool or how it relates to gsites_set_insert_point, which is a sibling that also governs placement.

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