Skip to main content
Glama

Quattr

market_share_overview

Read-only

How's our market share in a segment? Your share vs tracked competitors, the segment leader, and the gap — sliceable by keyword, page, search intent, content category, or branded vs non-branded demand. Pass category:'' to scope share-vs-competitors to ONE content category (e.g. "how do we rank vs competitors in our Products content?"), or page:'' for one page/URL. Country and device are NOT supported here: the verb rejects them rather than returning whole-segment share under a geography or device claim. For a country ranking use market_share_breakdown(breakdown_by:"country"); for queries or pages in one country or device use that breakdown plus country/device. Share vs competitors only. If the question also wants clicks or traffic, use growth_vs_market_share instead. To rank ACROSS the values of a grouping (e.g. top intents or top categories by share), use market_share_breakdown. Defaults to the primary 'default' (Overall Market) segment when omitted — name another tracked segment to scope to it. UNIT CONTRACT: market-share values are already percentage units on a 0–100 scale (0.03 means 0.03%, not 3%); share delta is selected-minus-comparison percentage points; leader gap is leader-minus-client percentage points for the same period; only deltaPct is a relative-change ratio.

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": {
      "date_range": "<date_range>"
    },
    "name": "market_share_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoRestrict share-vs-competitors to ONE page/URL pattern (e.g. "%/products%"), matched against the customer page at the same summary grain used by QWA. Single-value filter.
brandNoRestrict to branded ("Yes") or non-branded ("No") demand (ignored at site granularity)
grainNoGranularity: whole-segment (default), site, keyword or page. Keyword/page unlock keyword-, page- and intent/brand-sliced views; site is whole-site only. NOTE: 'category' is NOT supported for share-vs-competitors (no member carries content categories AND the comp{N} columns) — passing it returns a clear steer, not competitor shares.
deviceNoNOT supported on this summary. Accepted only so the request can be rejected instead of returning whole-segment share while a host claims that device. Use market_share_breakdown(breakdown_by:"keyword"/"page") plus device.
intentNoRestrict to ONE search intent, e.g. "Informational" (a single-value filter, not a breakdown — for top-N across intents use market_share_breakdown; ignored at site granularity)
mediumNocompetitor source medium for the comparison, e.g. "google/organic" (default) or "google/cpc"
countryNoNOT supported on this summary. Accepted only so the request can be rejected instead of returning whole-segment share while a host claims that country. Use market_share_breakdown(breakdown_by:"country"), or breakdown_by:"keyword"/"page" plus country.
segmentNoTracked segment ID; omit to use the primary "default" (Overall Market) segment.
categoryNoRestrict share-vs-competitors to ONE content category (e.g. "Products"), as exposed by list_filter_values(category). Uses QWA's summary-level category parameter. Single-value filter — for top-N across categories use market_share_breakdown(breakdown_by=category). Resolve the exact value with list_filter_values first.
date_rangeYesExplicit date range, e.g. "2026-05-01 to 2026-05-31". Both endpoints are INCLUSIVE — the END day is covered (a 7-day range = 7 days). Quattr weeks run Sunday–Saturday; for "last week" use the most recent complete Sun–Sat span.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare a safe read-only profile, but the description adds unusual value: it discloses that country/device are deliberately rejected rather than silently degrading to whole-segment share, documents the default 'default' segment behavior, and provides a full unit contract (0–100 percentage scale, delta in pp, leader gap in pp, only deltaPct is relative).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the guiding question and the value proposition, then layers exclusions and the unit contract. It is dense and slightly repetitive (country/device rejection is restated), but every block earns its place for a 10-parameter tool.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so via the explicit UNIT CONTRACT covering share, delta, leader gap, and deltaPct. Combined with scoping rules and alternatives, an agent has everything needed to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: worked examples for category and page scoping, the default-segment behavior, and the unit semantics of the returned share/delta/gap values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening states a precise verb+resource: share vs tracked competitors, the segment leader, and the gap. It distinguishes itself from siblings by naming market_share_breakdown, growth_vs_market_share, and market_share_query with the conditions that select them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit when-to-use and when-not-to-use: country and device are rejected here, with concrete redirects (market_share_breakdown(breakdown_by:"country") plus country/device). It also routes click/traffic questions to growth_vs_market_share and cross-grouping rankings to market_share_breakdown.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources