google-search-console-mcp

Overview Schema Source Related Servers Discussions Admin

Add a property

add_site

Idempotent

Adds a site property to Google Search Console without verifying ownership. Use this to register an unverified property; ensure ownership verification is completed to access data.

Instructions

Adds a property to Search Console. This does NOT verify ownership: unless the credential already owns the domain, the property lands as siteUnverifiedUser and every data call for it returns 403. To actually get a working property, use setup_site, which does this in the right order — get_verification_token, then the DNS record or HTML file, then verify_site, then this.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`site_url`	Yes	The property to create: "sc-domain:example.com" or "https://example.com/". Required — this one does not fall back to GSC_SITE_URL, because the property being created is by definition not the one you are already working with.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	Yes
`site`	Yes
`added`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.0Sep 8, 2026
- addedInput schema / properties / site_url / maxLength
```
Added value: +2048
```
First observedv0.2.0Sep 5, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations indicate readOnly=false, destructive=false, idempotent=true. The description adds crucial context: adding without verification results in siteUnverifiedUser and 403 errors on data calls, making the side effects and limitations clear.

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, front-loaded with the core action and resource, then immediately noting the caveat and alternative. No wasted words, all sentences serve a purpose.

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?

Explains the consequence of using this tool (unverified property) and provides the full alternative path via setup_site. Complete guidance for an agent deciding between add_site and setup_site, with output schema present but not needing explanation.

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?

Schema covers the single parameter site_url with a description including format examples. The tool description does not add extra parameter semantics beyond the schema, so baseline score of 3 is appropriate.

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?

Clearly states the action 'Adds a property to Search Console' with a specific resource. Distinguishes from sibling setup_site by explicitly noting it does NOT verify ownership, so the agent understands the difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly says when to use this tool (to add a property) and when to use setup_site instead. Provides a sequence of operations (get_verification_token → verify_site → this) to achieve a working property.

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