searchconsole-mcp

Add a Search Console site

gsc_add_site

Add a site property to Google Search Console using domain or URL-prefix format, leaving it unverified until ownership is confirmed.

Instructions

Add a property to Search Console. Use "sc-domain:example.com" for domain properties or "https://www.example.com/" for URL-prefix properties. The property stays unverified until ownership is confirmed.

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

Input Schema

Name	Required	Description	Default
`siteUrl`	Yes	Property, e.g. sc-domain:example.com

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 23, 2026

TDQS

A4.2/5.0

Behavior3/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It mentions that the property stays unverified until ownership is confirmed, which is useful. However, it does not cover potential side effects (e.g., replacement, duplicate behavior), permissions, or reversibility—important for a mutation tool.

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?

Two sentences, no filler. The action is front-loaded, and the format guidance and verification note are directly relevant. Every word earns its place.

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 tool with a single parameter and no output schema, the description covers the essential usage and a key behavioral trait (unverified state). It omits potential edge cases like duplicate properties or error handling, but these are likely covered by the API itself. Overall, it is sufficiently complete for an agent to invoke it correctly.

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% (siteUrl is described), so baseline is 3. The description adds real value by explaining the two accepted formats and their distinctions (sc-domain: vs https://), which goes beyond the schema's single example. This clarifies acceptable input and reduces ambiguity.

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?

The description clearly states the action ('Add a property to Search Console') with a specific resource and verb, and distinguishes itself from siblings like list, remove, or analyze tools. It also provides concrete URL format examples, making the tool's scope unmistakable.

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?

The description gives clear context on how to form the siteUrl (domain vs. URL-prefix) and notes the verification status, implying when the tool is appropriate (adding a property). It does not explicitly state when not to use it or name alternative tools, but the purpose is distinct enough that an agent can infer usage.

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

Deploy Server