Skip to main content
See Filter Compatibility for the authoritative Measure date-filter contract and the coverage of every MCP tool.
The Measure tools surface connected web analytics alongside AI visibility data: search performance, classified AI-referral traffic, supported revenue attribution, and observed AI crawler occurrences. They read from integrations you connect inside Qwairy under Measure.
Connection required. Each tool depends on its corresponding integration: Google Search Console, Bing Webmaster Tools, a supported analytics provider, or Crawler Analytics. After OAuth scope, brand access, and plan or entitlement checks pass, an absent integration is rendered as not connected with empty data so an assistant can explain what to connect. Missing scope, brand access, or product eligibility can return an error instead.
All Measure tools require the read:measure scope. Existing OAuth connections created before this scope must reconnect to use them.
Qwairy MCP returns each tool result as rendered Markdown in content[0].text; it does not currently include JSON structuredContent. The tables below describe the values rendered for the reader, not a stable JSON wire schema. Do not parse the Markdown as an application data contract.

get_search_console_metrics

Google Search Console performance for the brand’s site: clicks, impressions, CTR, and average position, broken down by search query or by page.

Parameters

Returns

Example prompts

OAuth scope

Requires: read:measure

get_bing_metrics

Bing Webmaster Tools search performance for the brand’s site, by query or by page. Same shape as get_search_console_metrics, sourced from Bing.

Parameters

Returns

OAuth scope

Requires: read:measure

get_referrer_analytics

Google Analytics sessions classified from recognized AI referrers, compared with total site sessions in the selected scope.

Parameters

Returns

Example prompts

OAuth scope

Requires: read:measure

get_ai_revenue

Configured business conversions attributed to AI-referral traffic from a connected analytics provider. The tool keeps provider-native measured revenue separate from estimated value calculated from your fixed-value conversion definitions.

Parameters

Returns

When no supported provider is connected, the rendered result tells the reader to connect one and omits metric sections. When a provider is connected but the selected period has no included conversions, measured revenue, or estimated value, it renders an empty-period notice and zero-valued outcome metrics. These states are not equivalent.
For GA4, this MCP tool currently uses Direct session attribution. The dashboard defaults to Combined attribution, which falls back from an AI session source to an AI first-user source. Align the attribution mode before comparing MCP and dashboard totals.
Provider-native measured revenue and configured fixed-value estimates are separate. A fixed value is multiplied by AI conversions and uses the configured estimate currency. Measured revenue remains in the provider currency, which is currently rendered without a currency code. Do not add the two values unless you have independently confirmed that their currencies match.

Example prompts

OAuth scope

Requires: read:measure

get_crawler_activity

Read retained, site-wide lifecycle aggregates for supported observable AI-specific User-Agent identities such as GPTBot, ClaudeBot, PerplexityBot, and OAI-SearchBot. This tool does not expose raw HTTP logs and does not establish why a request occurred, whether content was indexed, or whether a later answer was caused by that occurrence.
Google-Extended is a robots-control token, not a separately observable crawler User-Agent. A robots.txt rule for that token does not create an occurrence in Crawler Analytics.

Parameters

Returns

firstSeen, lastSeen, and occurrences describe retained aggregates, not a queryable raw-log history. Treat them as observation evidence only, without inferring indexing, model training, citations, or causality.

Example prompts

OAuth scope

Requires: read:measure

get_page_performance

Per-page observed AI crawler occurrences, with lifecycle state and top supported crawler identities for each rendered page. Complements get_crawler_activity with a page-level retained-rollup view.
This tool requires an active Business, Enterprise, or Agency Business plan, or an explicit Crawler Analytics feature override, in addition to read:measure and access to a live brand.

Parameters

Returns

The headline’s page count is the durable page-identity inventory before limit, including neglected identities and identities without an occurrence in the selected period. It is not pages.length or the number of pages carrying the displayed occurrences.
The current-page query first selects up to limit identities by selected-period occurrences, then removes neglected identities, so the rendered table can contain fewer than limit rows. The neglected table comes from a separate query ordered by oldest lastSeenAt and can be non-empty even when the selected period has no rollup.
Crawler Analytics must be active, not disabled, and have an active non-revoked key to be connected. No HTTP events are retained or returned. Sensitive-looking or overlong paths can be pseudonymized; do not reconstruct or link them, and expect no title for those rows.

Example prompts

OAuth scope

Requires: read:measure
Each tool above mirrors a dashboard page in the Measure section: