google_search_console_get_search_analytics

Description

Query Google Search Console search analytics data. Returns clicks, impressions, CTR, and position. Args: site_url (string, required): The Search Console property URL. start_date (string, required): Start date in YYYY-MM-DD format. end_date (string, required): End date in YYYY-MM-DD format (must be >= start_date). dimensions (array, optional): Group by dimensions. Valid: query, page, device, country, date, searchAppearance. Note: searchAppearance cannot be combined with query, page, device, or country — only with date. search_type (string, optional): web (default), image, video, news, discover, googleNews. dimension_filter_groups (array, optional): Filter by dimension values. Note: Cannot combine aggregate_by=byPage with a page dimension filter. aggregate_by (string, optional): auto (default), byPage, byProperty, byNewsShowcasePanel. row_limit (int, optional): Rows per page. Range: [1, 25000]. Default: 25. cursor (string, optional): Opaque cursor from a previous response's pagination.nextCursor. Omit for the first page; never construct one by hand. Returns: data: array of { keys, clicks, impressions, ctr, position } rowCount: rows in this page (Search Console reports no grand total) pagination: { hasMore, nextCursor? } — nextCursor is absent on the last page responseAggregationType, firstIncompleteDate (if data is incomplete) Pagination: when pagination.hasMore is true, call again with the same parameters plus cursor set to pagination.nextCursor. A cursor only continues the exact call that returned it — changing the dates, dimensions or filters invalidates it, and the call is rejected rather than silently returning rows from a different query. IMPORTANT — when you need a complete, consistent result set, raise row_limit and take it in ONE call rather than crawling. Search Console sorts rows by clicks descending and orders ties "in an arbitrary way", and that tie order is not stable between calls. Since most rows on a typical property have 0 clicks, they are nearly all tied, so a multi-page crawl can repeat some rows and miss others. A single call has no such problem: one call, one ordering. row_limit goes up to 25000. Use the cursor for browsing, or when the result genuinely exceeds one page, and treat a crawled set as approximate rather than exact. Note: Data freshness lag — recent dates (last 3+ days) may be incomplete. Check firstIncompleteDate in response.

Usage

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "google_search_console_get_search_analytics",
    "arguments": {
      "site_url": "https://example.com/",
      "start_date": "2024-01-01",
      "end_date": "2024-01-31",
      "reason": "Get overall search performance"
    }
  }
}

hopkin google ch-console-get-search-analytics

{
  "mcpServers": {
    "google-search-console": {
      "url": "https://gsc.mcp.hopkin.ai",
      "transport": "sse"
    }
  }
}

Parameters

Examples

{
  "site_url": "https://example.com/",
  "start_date": "2024-01-01",
  "end_date": "2024-01-31",
  "reason": "Get overall search performance"
}

{
  "site_url": "https://example.com/",
  "start_date": "2024-01-01",
  "end_date": "2024-01-31",
  "dimensions": [
    "query"
  ],
  "reason": "Get top queries"
}

{
  "site_url": "https://example.com/",
  "start_date": "2024-01-01",
  "end_date": "2024-01-31",
  "dimensions": [
    "page"
  ],
  "reason": "Get top pages"
}

{
  "site_url": "https://example.com/",
  "start_date": "2024-01-01",
  "end_date": "2024-01-31",
  "dimensions": [
    "query"
  ],
  "cursor": "<pagination.nextCursor from the previous response>",
  "reason": "Continue a crawl past the first page"
}