Pixelesq

Get search performance

get_search_performance

Read-only

Get Google Search Console search performance data (clicks, impressions, CTR, position): totals with the change against the previous period, and the top queries, pages, devices and countries, most clicks first, then most impressions

Input Schema

Name	Required	Description	Default
`period`	No	Time period	LAST_28_DAYS
`projectId`	Yes	The project ID

Output Schema

Name	Required	Description
`byPage`	No
`period`	No
`totals`	No
`byQuery`	No
`message`	No	Why there is no data, in place of the data
`warning`	No	Set when the connected Search Console property does not cover the address the site is served at
`byDevice`	No
`byCountry`	No
`ctrChange`	No
`clicksChange`	No
`positionChange`	No
`dataFreshnessDate`	No
`impressionsChange`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 22, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "byCountry": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "clicks": {
+            "type": "number"
+          },
+          "ctr": {
+            "type": "number"
+          },
+          "impressions": {
+            "type": "number"
+          },
+          "keys": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "position": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "byDevice": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "clicks": {
+            "type": "number"
+          },
+          "ctr": {
+            "type": "number"
+          },
+          "impressions": {
+            "type": "number"
+          },
+          "keys": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "position": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "byPage": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "clicks": {
+            "type": "number"
+          },
+          "ctr": {
+            "type": "number"
+          },
+          "impressions": {
+            "type": "number"
+          },
+          "keys": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "position": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "byQuery": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "clicks": {
+            "type": "number"
+          },
+          "ctr": {
+            "type": "number"
+          },
+          "impressions": {
+            "type": "number"
+          },
+          "keys": {
+            "items": {
+              "type": "string"
+            },
+            "type": "array"
+          },
+          "position": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "clicksChange": {
+      "additionalProperties": {},
+      "properties": {
+        "change": {
+          "type": "number"
+        },
+        "current": {
+          "type": "number"
+        },
+        "previous": {
+          "type": "number"
+        },
+        "trend": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "ctrChange": {
+      "additionalProperties": {},
+      "properties": {
+        "change": {
+          "type": "number"
+        },
+        "current": {
+          "type": "number"
+        },
+        "previous": {
+          "type": "number"
+        },
+        "trend": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "dataFreshnessDate": {
+      "type": "string"
+    },
+    "impressionsChange": {
+      "additionalProperties": {},
+      "properties": {
+        "change": {
+          "type": "number"
+        },
+        "current": {
+          "type": "number"
+        },
+        "previous": {
+          "type": "number"
+        },
+        "trend": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Why there is no data, in place of the data",
+      "type": "string"
+    },
+    "period": {
+      "type": "string"
+    },
+    "positionChange": {
+      "additionalProperties": {},
+      "properties": {
+        "change": {
+          "type": "number"
+        },
+        "current": {
+          "type": "number"
+        },
+        "previous": {
+          "type": "number"
+        },
+        "trend": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "totals": {
+      "additionalProperties": {},
+      "properties": {
+        "clicks": {
+          "type": "number"
+        },
+        "ctr": {
+          "type": "number"
+        },
+        "impressions": {
+          "type": "number"
+        },
+        "position": {
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "warning": {
+      "description": "Set when the connected Search Console property does not cover the address the site is served at",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: results include a comparison against the previous period and are sorted most-clicks-first then most-impressions. It stops short of stating what happens when GSC is not connected or when no data exists.

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 with the resource front-loaded and the returned dimensions trailing as a list; no filler. The enumerated output facets make it long, but each element carries information an agent would otherwise have to open the output schema to learn.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present and annotations covering safety, the description need not explain return values, and it is adequate for calling the tool. However, in a 60+ tool surface it omits the GSC-connection precondition and project-sourcing step that would let an agent chain correctly from get_gsc_connection_status / list_projects.

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 both parameters are already documented and the baseline is 3. The phrase 'change against the previous period' loosely gestures at the period parameter, but the description never mentions the period options (7/28/90 days) or the default, so it adds no real semantics beyond the schema.

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 verb and resource (Google Search Console search performance data) and enumerates exactly what is returned: totals with period-over-period change plus top queries, pages, devices and countries. This clearly distinguishes it from the broader get_site_analytics and get_ai_referral_analytics siblings without needing to name them.

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 only implied by the resource name — an agent infers this is the read path for GSC search metrics. There is no explicit 'use this instead of get_site_analytics when...' guidance, and no mention of the apparent prerequisite implied by the get_gsc_connection_status sibling or of where projectId comes from.

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

All Pixelesq tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?