"Google Search Console" matching MCP tools:

• list_propertiesA

  QuerySail: Google Search ConsoleA

  Use this when the user asks which Google Search Console sites or properties they can access, or to find the exact property_id for a site. Returns exact property IDs (Domain properties look like 'sc-domain:example.com', URL-prefix properties like 'https://example.com/'), the permission level, and connection status. The same site is listed once even if several connected Google accounts can see it. A site name can match more than one property, for example a Domain property and a URL-prefix property. Read-only. Does not change anything in Google Search Console.

  ConnectorOAuth

• get_keyword_rankingsA

  BlogSEOA

  Rank-tracking view from Google Search Console, covering the website's tracked keywords only and refreshed at the Search Console sync cadence (see gsc_last_synced_at): for each keyword the current average position, the page ranking for it, clicks, impressions, ctr (clicks / impressions), the country of that snapshot and the last sync time. Pass keyword_ids (max 50) or get the top N keywords (default 50, max 50). Filters run in the database: position_min and position_max bound the current position (unranked keywords are excluded when either is set), min_impressions drops low-visibility keywords, and sort orders by position (best first, unranked last, default), impressions or clicks (highest first). Page-2 quick wins: position_min 5, position_max 15, min_impressions 200, sort impressions. position_30d_ago is included when a history point exists around 30 days ago for the snapshot country (or the country you pass, lowercase alpha-3 like usa, or wwd). Not for changes over time: use get_keyword_trends for click, impression and position deltas between periods. Tells you when Google Search Console is not connected instead of returning empty positions silently. Pass website_id when the account has several websites (see get_account).

  ConnectorOAuth

• get_keyword_trendsA

  BlogSEOA

  Google Search Console trend view for the website's tracked keywords, refreshed at the Search Console sync cadence: compares the last window_days (7, 28 or 90, default 28) with the window_days before it. Per keyword: clicks, impressions and impression-weighted average position in both windows plus the deltas (current minus previous), and the page currently ranking for it. by_page groups the clicks and impressions of every keyword with data by that page, most decayed first (clicks_delta ascending), so it answers which pages are losing traffic. Pass keyword_ids (max 200) or let it consider every keyword with history; rows are sorted by clicks_lost (default), clicks_gained, position_lost or position_gained and cut to top (default 50, max 200). by_page is computed before the cut. Rows use each keyword's snapshot country, or the country you pass (lowercase alpha-3 like usa, or wwd). Keywords without history in either window are omitted; a position is null when its window has no impressions. Search Console data lags 2 to 3 days, so the newest days of the current window are usually missing. Not for the current position or ctr (use get_keyword_rankings) nor volume and difficulty (use list_keywords). Tells you when Google Search Console is not connected instead of returning empty rows silently. Pass website_id when the account has several websites (see get_account).

  ConnectorOAuth

• marketing_get_reportA

  Google Analytics (unofficial)A

  Primary reporting tool for a given GA4 property or site. Use for totals, trends, and breakdowns by dimension across GA4 website traffic and app analytics, Google Search Console site traffic, and Bing Webmaster — including last-30-days summaries, revenue, leads, sessions, users, engagement/time-on-page (average_session_duration, user_engagement_duration), and period-over-period comparisons. Drill deep: GA4 supports up to 9 grouped dimensions (date/hour, geo, device/browser/OS, source/medium/channel, landing_page/page_path, etc.). Defaults to all mapped connected sources merged into one standardized view, aligned on the shared grain (typically landing_page) so a page row blends GA4 sessions+engagement with Search Console/Bing clicks/impressions/CTR/position; per-source detail (e.g. full query lists) stays in sourceSections. Note GA4 has no `query` dimension and Search Console/Bing have no sessions/engagement, so those cannot share one row — query is a Search Console/Bing breakdown. Narrow with sources or sourceMode='single'. Any GA4 dimension/metric name not in the catalog is passed through to the GA4 API automatically; metricMode='source_native' forces a pure GA4-native report. Pass one date range for a single window or two date ranges for period-over-period comparison.

  ConnectorNo auth

• save_keywordsA

  MarkA

  Saves keywords (from research or Search Console) and sets their tags, exclusion and rank tracking, in one call. New keywords are tracked and audience-checked (one Google top 10 fetch each) unless track is false or they are excluded. Exclude a keyword whose searchers aren't the buyer; it stops tracking. If this refuses because the workspace is not set up, call get_setup_status. Related: research_keywords, list_saved_keywords, set_up_market.

  ConnectorOAuth

• query_search_consoleA

  BlogSEOA

  Queries Google Search Console live for the website: clicks, impressions, click-through rate and average position over any period of the last 16 months, grouped by query, page, country, device, date or search appearance, with filters on any of them (contains, equals, regex). It reads everything Search Console has at the moment of the call, where get_keyword_rankings and get_keyword_trends only cover the tracked keywords synced once a day. It also works on a website that has no plan yet, as soon as Search Console is connected for it. Examples: the queries of one page (dimensions ["query"], filter page equals its URL); queries ranking 5 to 15 with the most impressions (position_min 5, position_max 15, sort impressions); brand versus non-brand (filter query includingRegex or excludingRegex); daily clicks (dimensions ["date"]); pages losing traffic (call it for two periods and compare). Rows come back ordered by clicks, or by date when grouping by date only, unless sort is set. min_clicks, min_impressions, position_min, position_max and sort are applied to the top 25000 rows by clicks, and the result says when the property had more. Returns at most 500 rows per call (page with start_row). Search Console data lags 2 to 3 days. Limited to 200 calls per hour per website. When Search Console is not connected, the error gives the page where an admin connects it. Pass website_id when the account has several websites (see get_account).

  ConnectorOAuth

• get_performanceA

  QuerySail: Google Search ConsoleA

  Use this to retrieve Google Search Console search performance (clicks, impressions, CTR, average position) for one property. With no dimensions it returns property totals. Add dimensions to break results down by date, hour, query, page, country, device or searchAppearance, and filters to narrow to specific queries, pages, countries, devices or search appearances (for example mobile traffic to pages containing '/blog/'). search_type selects web (default), image, video, news, discover or googleNews results; discover and googleNews have no queries. For what happened in the last hours or days, group by hour (data_state 'hourly', last 10 days only, preliminary). Dates are Pacific Time. If no dates are given it uses the last 28 finalized days (or yesterday and today for hourly) and reports the exact dates it used. Covers one period at a time. Rows are bounded (default 20, max 100); page through with the returned cursor. Google returns only top rows for query/page breakdowns, so results are not guaranteed to be complete, and a missing row does not mean zero. Figures are observed values and do not identify causes. Read-only; cannot request indexing or change anything in Search Console.

  ConnectorOAuth

• compare_performanceA

  QuerySail: Google Search ConsoleA

  Use this when the user asks what changed between two periods, why traffic went up or down, or which pages, queries, countries or devices gained or lost. Compares clicks, impressions, CTR and average position for one property between a current period and the previous period (default), the same weekdays a year earlier, or explicit dates. Returns both totals with absolute and percent changes, the click change split into an impressions part and a CTR part, and, with a dimension, the top gainers and losers ranked by change in clicks or impressions. Dates are Pacific Time; with no dates the current period is the last 28 finalized days. Filters and search type apply to both periods. Changes are observed differences and do not identify causes. Read-only; does not change anything in Search Console.

  ConnectorOAuth

• google-maps.place_typesA

  Vee3A

  List supported Google Maps place type values for search filters. Returns place_types as a string array. Use a value with place_type on google-maps.search or google-maps.nearby_search. Cost = 1 token.

  ConnectorNo auth

• google-search-console.list_sitemapsA

  Vee3A

  List sitemaps submitted for a Search Console property. Call google-search-console.list_sites to discover sites. Omit site_url to use the default property, or pass an exact site_url from that response. Returns sitemap paths plus submission, download, warning, and error details. Use an exact path from this response with get_sitemap, submit_sitemap, or delete_sitemap. Cost = 5 tokens.

  ConnectorNo auth

• google-search-console.list_sitesA

  Vee3A

  List Search Console properties for this account. Returns Vee3-managed domains plus sites added with google-search-console.add_site. Call this to discover sites, then omit site_url on later calls to use the default property, or pass an exact site_url from this response. If no properties appear, add a site with google-search-console.add_site or register a domain with domains.register. Cost = 5 tokens.

  ConnectorNo auth

• get_search_consoleA

  KleapA

  Use this when the user asks how their site is doing IN GOOGLE SEARCH — keywords/queries they rank for, impressions, clicks from search, CTR, or average position. Backed by their own Google Search Console property (connected per site in Kleap's options), so it is the real Google data, not an estimate. Returns totals plus the top queries and top pages that produced them. Search Console lags real traffic by ~2 days — the newest days are always incomplete, say so rather than reporting a drop. If connected is false or site_selected is false, the site simply has no Search Console hooked up: call connect_search_console(app_id) — it returns a consent_url to hand the user, and that is the whole setup. Do NOT send them hunting through Kleap's settings for it. For visitors and pageviews on the site itself (all sources, not just Google), use get_analytics instead. Requires the analytics:read scope — on a 403 INSUFFICIENT_SCOPE error, tell the user to disconnect and reconnect the Kleap integration (re-authorize).

  ConnectorOAuth

• get_search_consoleA

  KleapA

  Use this when the user asks how their site is doing IN GOOGLE SEARCH — keywords/queries they rank for, impressions, clicks from search, CTR, or average position. Backed by their own Google Search Console property (connected per site in Kleap's options), so it is the real Google data, not an estimate. Returns totals plus the top queries and top pages that produced them. Search Console lags real traffic by ~2 days — the newest days are always incomplete, say so rather than reporting a drop. If connected is false or site_selected is false, the site simply has no Search Console hooked up: call connect_search_console(app_id) — it returns a consent_url to hand the user, and that is the whole setup. Do NOT send them hunting through Kleap's settings for it. For visitors and pageviews on the site itself (all sources, not just Google), use get_analytics instead. Requires the analytics:read scope — on a 403 INSUFFICIENT_SCOPE error, tell the user to disconnect and reconnect the Kleap integration (re-authorize).

  ConnectorNo auth

• list_keywordsA

  BlogSEOA

  Lists the website's tracked keywords (Google, in the website's default locale) with volume, difficulty, CPC, opportunity score/label, search intent, favorite flag, topic cluster label and the latest Google Search Console position, clicks, impressions and top ranking page. Pages of 50; sort by opportunity (default), volume, position (best first, unranked last) or recent. Use search to filter by keyword text and favorites_only to keep starred keywords. Positions are null when Google Search Console is not connected. Returns keyword_id values used by every other keyword tool. Pass website_id when the account has several websites (see get_account).

  ConnectorOAuth

• get_keywordA

  BlogSEOA

  Returns one keyword with its metrics, the last 90 days of Google Search Console position history (per day and country), the scheduled and generated articles targeting it, and up to 20 sibling keywords of the same topic cluster. Position history is empty when Google Search Console is not connected. Pass website_id when the account has several websites (see get_account).

  ConnectorOAuth

• list_gsc_sitesA

  AdLoopB

  List all Google Search Console properties the authenticated user can access. Serves as the discovery step for the site URLs that search analytics reports (run_gsc_report) take. Returns the site URL and permission level for each property. Search Console API: https://developers.google.com/webmaster-tools

  ConnectorAPI key

• marketing_dataA

  Agentcy - Your AI Marketing AgentA

  Query marketing data and analyze any website — analytics, SEO, advertising, e-commerce, CRM, social media, site health & brand identity, competitive intelligence, content creation, and data visualization. Always use a single call, even when the question spans multiple data sources or channels (e.g., GA4 + Google Search Console + Google Ads + CRM). The server auto-routes internally to all needed sources and returns a combined response with the same depth and granularity as individual queries — do NOT split multi-source or multi-channel questions into separate calls.

  ConnectorOAuth

• find_keyword_cannibalizationA

  BlogSEOA

  Finds tracked keywords for which two of the site's own pages will compete. This is BlogSEO's definition, not Search Console's "two URLs for one query" (Search Console gives one top page per keyword): a keyword is cannibalized when the page Google already ranks for it is not the landing page and is either a blog article (any position) or another page ranking within the website's cannibalization_max_position (top 30 by default), AND a BlogSEO article targets that same keyword without being the ranking page (with include_planned, a still-scheduled article counts too). Scans the Google keywords of the default locale that have a Search Console ranking page; snapshots older than 30 days are ignored, so it needs a recent sync. Returns up to top keywords (max 200), best position first, each with the ranking URL and its kind (blog_article or other_page), ranking_article_id when the ranking page is a BlogSEO article, the competing articles (article_id, headline, slug, status, live url when known; status scheduled means article_id is a scheduled_article_id) and a deterministic suggestion with its reason: consolidate when a published article competes with a ranking blog article, differentiate otherwise (for a planned article: rewrite its brief or drop the plan). Tells you when Search Console is not connected instead of returning nothing silently. Not a rank tracker: use get_keyword_rankings for positions and get_keyword for one keyword's articles. Pass website_id when the account has several websites (see get_account).

  ConnectorOAuth

• list_integrationsA

  BlogSEOA

  Lists the CMS, e-commerce and webhook integrations connected to the website's organization (provider, connection status, auto-publish and draft-mode flags, publishing targets such as blogs or collections) plus the Google Search Console connection of the website (property, status, last sync). Use it to know where articles get published and whether Search Console analytics are available. Credentials and tokens are never returned. A custom webhook or the hosted blog can be connected with connect_custom_webhook and create_hosted_blog; other integrations are connected, and any integration disconnected, in the app. Pass website_id when the account has several websites (see get_account).

  ConnectorOAuth

• get_app_contextA

  AutarioA

  The data map behind ONE autario app, so you can query app-first instead of guessing across thousands of datasets. Returns the app manifest (what it consumes, which connector providers it reads | Google Search Console, GA4, Google Ads, Meta Ads, YouTube, TikTok, Instagram, Facebook, Shopify, LinkedIn, Bing) and, for an authenticated caller, YOUR OWN reality behind it: your connector-instance tables (per-operation table with column list, row count, backing dataset_id and last refresh), your saved artifacts in the app, and 2-3 ready-to-run query examples on existing endpoints (query the dataset_id with query_dataset or GET /datasets/:id/data). Secrets and credentials are never included. Unauthenticated callers get the public manifest view. Use when a user asks "what does my <app> run on", "what data is behind <app>", "query my Search Console data" (Audience 360), or before analyzing any app-connected data. app ids come from list_apps.

  ConnectorNo auth

• get_platform_cutsA

  royaltea-publicA

  The current storefront/platform revenue cuts RoyalTea models — Steam, Epic Games Store (+ First Run), Apple, Google Play, console, itch.io — with exact tiers, thresholds, and the Unreal Engine royalty. Use to explain or cite what a given platform takes.

  ConnectorNo auth