Skip to main content
Glama
Sign In
ga4-mcp

ga4-mcp

by chimpmatic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

gsc_add_site

Add a site to Google Search Console by providing its URL in either URL prefix (e.g., https://example.com/) or domain property (e.g., sc-domain:example.com) format.

Instructions

Adds a site to Google Search Console. Use URL prefix (e.g. "https://example.com/") or domain property (e.g. "sc-domain:example.com").

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

Input Schema

NameRequiredDescriptionDefault
site_urlYesSite URL to add (URL prefix or sc-domain: format)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.8/5.0
Behavior2/5

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

No annotations present; description mentions mutation ('adds') but does not disclose side effects (e.g., duplicate handling, verification requirements, rate limits), leaving behavioral gaps for an agent.

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 concise sentences with front-loaded verb and resource, no extraneous information.

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?

Given low complexity (single param, no output schema), description adequately covers purpose and input format; minor gap in explaining response/error behavior.

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 covers 100% of single parameter; description adds examples and format clarification beyond schema description, enhancing agent understanding.

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 ('Adds a site') and resource ('to Google Search Console'), with specific format examples (URL prefix or domain property), distinguishing it from sibling tools like gsc_list_sites.

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

Usage Guidelines3/5

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

Provides guidance on parameter format (URL prefix vs. domain property) but lacks when-to-use or when-not-to-use context relative to sibling tools such as gsc_list_sites or gsc_inspect_url.

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

Deploy Server

Other Tools