Skip to main content
Glama
Sign In
ga4-mcp

ga4-mcp

by chimpmatic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

indexing_notify

Send URL update or deletion notifications to Google for immediate crawling via the Indexing API.

Instructions

Notifies Google to crawl or remove a URL via the Indexing API. Requires service account with indexing scope.

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": {
      "url": "<url>"
    },
    "name": "indexing_notify"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL to notify Google about
typeNoNotification type (default: URL_UPDATED)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior2/5

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

No annotations provided, so description carries full burden. Mentions service account requirement but does not disclose side effects, rate limits, or that only verified site owners can use it. Insufficient for safe invocation.

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 no redundant information. Every word adds value.

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 no output schema and simple two-parameter tool, description covers purpose and prerequisite adequately. Could mention response format or error conditions for full completeness, but acceptable.

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 coverage is 100%, so baseline is 3. Description adds no extra meaning about parameters beyond what schema provides. Enum values are not explained.

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?

Description clearly states the tool notifies Google to crawl or remove a URL via the Indexing API. It distinguishes from siblings like `indexing_status` which checks status rather than triggers actions.

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?

Describes a prerequisite (service account with indexing scope) but does not explicitly state when to use this tool vs alternatives like `indexing_status`. Usage is implied but lacks explicit guidance.

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