Skip to main content
Glama

Search Console: Add site

gsc_add_site
Idempotent

Add a site to Search Console FOR one of this agency's clients, and link it to that client. Takes the client's name and the new site (https://example.com/ for a URL-prefix property, sc-domain:example.com for a Domain property). The site is added UNVERIFIED; follow with site_verification_token and site_verify. Previews unless confirm is true.

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": {
      "client": "<client>",
      "new_site_url": "<new_site_url>"
    },
    "name": "gsc_add_site"
  }
}

Input Schema

NameRequiredDescriptionDefault
clientYesClient name from list_clients — the site is added for, and linked to, this client
confirmNoLeave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change.
new_site_urlYesThe site to add, e.g. https://example.com/ or sc-domain:example.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / confirm / description
      Added value: +"Leave false to preview: nothing changes and the preview shows exactly what would happen. Set true only after the user has agreed to this exact change."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare non-readOnly, idempotent, non-destructive, open-world. The description adds context the annotations cannot: the site lands in an UNVERIFIED state, the required follow-up verification calls, and the preview-unless-confirm gate. That is exactly the extra behavioral disclosure the bar rewards.

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, front-loaded with the core action, then format guidance, then state/workflow behavior. No filler and nothing buried.

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?

With no output schema and full annotation coverage, the description still conveys the essential workflow (add unverified → verify) and the preview/confirm gate. Nothing an agent needs to call this correctly is missing.

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 100%, so baseline is 3, but the description goes further by explaining the two property formats (https://example.com/ for URL-prefix vs sc-domain:example.com for Domain) and the client/site linkage semantics. This adds real meaning beyond the schema's bare examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Add a site to Search Console') with explicit scope ('FOR one of this agency's clients') and the linking side-effect. This cleanly distinguishes it from gsc_query, gsc_list_sitemaps, site_verify, and site_verification_token, which are the adjacent Search Console siblings.

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?

Names the downstream workflow explicitly ('follow with site_verification_token and site_verify'), which tells the agent this is the first step in a chain, and clarifies preview vs commit via confirm. It stops short of stating exclusions or when NOT to use it, but the sequencing guidance is clear.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.