gsc_search_analytics
Pack: google_search_console · Endpoint: https://gateway.pipeworx.io/google_search_console/mcp
Query Search Console search-performance data: clicks, impressions, CTR, and average position, grouped by dimensions. Use for “top queries/pages last month”, organic CTR, ranking trends. siteUrl must be exactly as returned by gsc_list_sites.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
siteUrl | string | yes | The property URL exactly as listed by gsc_list_sites (e.g. “https://example.com/” or “sc-domain:example.com”) |
startDate | string | yes | Start date, YYYY-MM-DD (inclusive). Search Console data lags ~2-3 days. |
endDate | string | yes | End date, YYYY-MM-DD (inclusive) |
dimensions | array | no | Group results by these dimensions (e.g. [“query”] for top queries, [“page”] for top pages, [“date”] for a time series). Default: none (totals). |
items | string | no | |
rowLimit | number | no | Max rows (default 25, max 25000) |
searchType | string | no | Search type / data state (default web) |
dimensionFilterGroups | array | no | Optional Search Console dimensionFilterGroups objects to filter rows (e.g. filter query contains “shoes”). Advanced; pass-through to the API. |
items | object | no |
Example call
curl -X POST https://gateway.pipeworx.io/google_search_console/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"gsc_search_analytics","arguments":{}}}'Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"google_search_console": {
"url": "https://gateway.pipeworx.io/google_search_console/mcp"
}
}
}See Getting Started for client-specific install steps.