Search Console: Query Search Analytics
gsc_query_search_analyticsFetch Search Console clicks, impressions, CTR and average position grouped by query, page, date, country or device to analyze search performance, with filters and row paging.
Instructions
Search performance for a property: clicks, impressions, CTR and average position, grouped by the dimensions you pick (date, hour, query, page, country, device, searchAppearance, brandedClassification). Rows come back with named fields ({query, page, clicks, impressions, ctr, position}), sorted by clicks (by date when grouped by date), plus returned_totals: the sum of the RETURNED rows only, not the property total (rows past row_limit are not counted, and query-grouped rows omit anonymized queries); and next_start_row when there may be more. Dates are Pacific-time calendar days; data lags 2-3 days and is kept 16 months; the default range is the 28 days ending 3 days ago. QUOTA: grouping or filtering by page or query, and long ranges, are the expensive part of the 10-minute and daily load quotas — ask for the dimensions you need, not all of them. The hour dimension needs data_state hourly_all (set for you) and covers only about the last 10 days, which is then the default range. To find what changed between two periods use gsc_compare_periods instead of two queries.
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": {
"site": "<site>"
},
"name": "gsc_query_search_analytics"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| site | Yes | The Search Console property, e.g. "sc-domain:example.com" (a domain property: every protocol and subdomain) or "https://www.example.com/" (a URL-prefix property: exactly that scheme, host and path). A bare "example.com" or a URL without its trailing slash is resolved against the properties this account can see, preferring the domain property; the response's `site` says which property was read. gsc_list_sites lists them. | |
| type | No | Which Google surface: web (default, Search's main results), image, video, news (the News tab in Search), discover, googleNews (news.google.com and the News app), webMultimodal (Lens, Circle to Search, image uploads). discover and googleNews have no query dimension and no position. | web |
| filters | No | Filters, all AND-ed together, e.g. [{"dimension":"page","operator":"contains","expression":"/blog/"}]. Filtering by page or query costs as much load quota as grouping by it. | |
| end_date | No | Last day, YYYY-MM-DD, inclusive, a calendar day in Pacific time (America/Los_Angeles) — Search Console's own day boundary, not UTC. | |
| row_limit | No | Rows to return (1-25000). Defaults to 100. Every row lands in the conversation, so raise it deliberately; page with start_row instead of asking for thousands. | |
| start_row | No | Zero-based row offset, for paging: pass the previous response's next_start_row. | |
| data_state | No | final (Google's default): finalized data only. all: include the fresh, still-changing last days. hourly_all: required by, and set automatically for, the hour dimension. | |
| dimensions | No | Group by these, in this order, e.g. ["query"] or ["page","device"]. Empty (the default) returns one row of property totals. Each row carries a named field per dimension. brandedClassification (BRANDED/NON_BRANDED) has data from 2026-02-21 on, only for properties with enough volume. | |
| start_date | No | First day, YYYY-MM-DD, inclusive, a calendar day in Pacific time (America/Los_Angeles) — Search Console's own day boundary, not UTC. | |
| aggregation | No | How results are aggregated. auto (Google's default) is by page when grouping or filtering by page, by property otherwise; byProperty cannot be used with page. |