Skip to main content
Glama
MoonEyes

google-ecommerce-mcp

by MoonEyes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search Console URL inspection

gsc_inspect_url
Read-onlyIdempotent

Inspect a URL's Google index status to check verdict, coverage, canonical, robots.txt, page fetch, and last crawl time.

Instructions

Google index status of one URL (URL Inspection API): verdict, coverage state, user and Google-selected canonical, robots.txt state, page fetch state and last crawl time. Quota: 2,000 inspections per day.

Input Schema

NameRequiredDescriptionDefault
urlYesFull URL to inspect; must belong to the configured Search Console property
site_urlNoSearch Console property, e.g. sc-domain:example.com or https://www.example.com/; empty uses the configured GSC_SITE_URL (or the client's site). With a client registry it must be one of the client's sites
client_idNoClient id from clients_list. Required when several clients are registered; empty uses the only client (or the environment variables when there is no client registry)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • addedInput schema / properties / client_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Client id from clients_list. Required when several clients are registered; empty uses the only client (or the environment variables when there is no client registry)",
+  "title": "Client Id"
+}
    • addedInput schema / properties / site_url
      Added value: +{
+  "default": "",
+  "description": "Search Console property, e.g. sc-domain:example.com or https://www.example.com/; empty uses the configured GSC_SITE_URL (or the client's site). With a client registry it must be one of the client's sites",
+  "title": "Site Url",
+  "type": "string"
+}
  2. Changed1 schema field changedv0.1.2
    • addedInput schema / properties / url / description
      Added value: +"Full URL to inspect; must belong to the configured Search Console property"
  3. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description usefully adds a hard operational constraint the annotations cannot express: a quota of 2,000 inspections per day. It does not, however, explain quota accounting or auth prerequisites beyond what the schema implies.

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, both front-loaded: purpose first, then the quota constraint. Nothing is padded and every clause carries information.

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 present, the description compensates by enumerating the returned fields, and it flags the daily quota. Combined with 100% schema coverage of inputs and full annotation coverage of the safety profile, an agent has everything needed to call this correctly.

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 description coverage is 100%, so the two optional parameters (site_url, client_id) and the required url are already fully documented in the schema. The description adds no additional parameter-level semantics, so the baseline 3 applies.

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 action and resource: 'Google index status of one URL (URL Inspection API)', scoping it to a single URL. It then enumerates exactly what the result contains (verdict, coverage state, canonicals, robots.txt state, page fetch state, last crawl time), which makes it unmistakable against data-oriented siblings like gsc_performance or gsc_sitemaps.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no sibling is named as an alternative. Usage is only implied by the scope phrase 'one URL', which a capable agent can infer but which is not spelled out.

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