Skip to main content
Glama
MoonEyes

google-ecommerce-mcp

by MoonEyes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Search Console performance

gsc_performance
Read-onlyIdempotent

Get Google Search Console clicks, impressions, CTR, and average position split by query, page, country, device, or date to analyze organic search performance.

Instructions

Google Search Console search performance for the configured property: clicks, impressions, CTR and average position, split by query, page, country, device or date. Returns the top rows, "totals" for the whole period (same filter, no split), "truncated", the unit and definition of each metric under "metrics", and a "date_range" in Pacific Time (Search Console's timezone) with "data_complete".

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum rows returned (1 to 1000); totals always cover the whole property
end_dateNoYYYY-MM-DD; empty means 2 days ago (Search Console data lag)
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)
dimensionsNoHow to split the results
start_dateNoYYYY-MM-DD; empty means 30 days ago (Pacific Time)
search_typeNoSearch type (sent to Google as `type`): web, image, video, news, discover or googleNewsweb
page_containsNoOptional: keep only pages whose URL contains this text

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 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 / search_type
      Added value: +{
+  "default": "web",
+  "description": "Search type (sent to Google as `type`): web, image, video, news, discover or googleNews",
+  "enum": [
+    "web",
+    "image",
+    "video",
+    "news",
+    "discover",
+    "googleNews"
+  ],
+  "title": "Search Type",
+  "type": "string"
+}
    • 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. Changed2 schema fields changedv0.3.0
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum rows returned (1 to 1000)"New value: +"Maximum rows returned (1 to 1000); totals always cover the whole property"
    • changedInput schema / properties / start_date / description
      Previous value: -"YYYY-MM-DD; empty means 30 days ago"New value: +"YYYY-MM-DD; empty means 30 days ago (Pacific Time)"
  3. Changed8 schema fields changedv0.1.2
    • addedInput schema / properties / dimensions / description
      Added value: +"How to split the results"
    • addedInput schema / properties / dimensions / items / enum
      Added value: +[
+  "query",
+  "page",
+  "country",
+  "device",
+  "date",
+  "searchAppearance"
+]
    • addedInput schema / properties / end_date / description
      Added value: +"YYYY-MM-DD; empty means 2 days ago (Search Console data lag)"
    • addedInput schema / properties / limit / description
      Added value: +"Maximum rows returned (1 to 1000)"
    • addedInput schema / properties / limit / maximum
      Added value: +1000
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / page_contains / description
      Added value: +"Optional: keep only pages whose URL contains this text"
    • addedInput schema / properties / start_date / description
      Added value: +"YYYY-MM-DD; empty means 30 days ago"
  4. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld, so the bar is lower, and the description goes well beyond them: it discloses that results are the top rows only, that a 'truncated' flag exists, that 'totals' cover the whole period with the same filter but no split, and that dates are reported in Pacific Time with a 'data_complete' field. It does not mention auth requirements or rate limits, but the return-shape transparency is substantive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence, front-loaded with what is measured, then the split options, then the return structure. Every clause (totals semantics, truncation, metric definitions, timezone) carries information; only minor tightening is possible.

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?

With no output schema, the description has to explain the return payload, and it does so for the key fields (totals, truncated, metrics, date_range/data_complete). Combined with 100% schema coverage on the eight input parameters, an agent has enough to call and interpret this tool, though routing guidance and pagination nuance are thin.

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 schema already documents all eight parameters including defaults, enum values, and the data-lag behavior. The description adds no syntax or constraint detail beyond what the schema provides, so 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?

The description names a specific verb+resource (Google Search Console search performance for the configured property) and enumerates the metrics and split dimensions returned. An agent can distinguish it from gsc_inspect_url, gsc_sites, or gsc_sitemaps without opening any schema.

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?

Usage is implied by the metric-and-dimension framing (pull aggregated GSC performance data), but there is no explicit when-to-use versus alternatives such as ga4_report or gads_performance, and no statement of prerequisites or exclusions. Adequate for an agent that already knows it wants GSC data, but it does not route.

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