Skip to main content
Glama

Read search analytics

get_search_analytics
Read-onlyIdempotent

Read connected Google Search Console or Bing Webmaster Tools clicks, impressions, CTR, average position, previous-period totals, daily trends, top queries and pages. Requires an existing connection on the Analytics page and an eligible analytics/API plan. Defaults to 30 days. Search dates follow the provider, not traffic timezones or filters. Google Web Search runs about two days behind. Bing totals and queries cover the entire property; blog pages come from weekly top-100 lists. Read coverage and warnings before attributing figures to the blog.

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": {
      "provider": "<provider>"
    },
    "name": "get_search_analytics"
  }
}

Input Schema

NameRequiredDescriptionDefault
rangeNo
providerYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive semantics, and the description still adds substantial context: connection/plan prerequisites, a two-day lag for Google Web Search, provider-defined date semantics that ignore timezones and filters, Bing's property-wide totals versus weekly top-100 lists for blog pages, and an instruction to read coverage and warnings before attributing figures. These are exactly the operational caveats an agent needs and cannot get from structured fields.

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?

Purpose and covered metrics are front-loaded, then prerequisites, then behavioral caveats, with no filler sentences. It is dense and slightly list-heavy, but each clause (provider dates, Google lag, Bing coverage limits) carries decision-relevant information.

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 only two parameters, no output schema, and a simple read operation, the description supplies everything missing elsewhere: what is returned, prerequisites, default range, and the interpretation caveats around latency and Bing/blog coverage. Nothing an agent needs to call or correctly interpret this tool is absent.

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 description coverage is 0%, so the description must carry meaning, and it does: 'Defaults to 30 days' explains the `range` default and implies day units, while 'Search dates follow the provider' and the Google/Bing framing explain what the required `provider` value selects. It stops short of describing the shorter/longer range enum trade-offs or plan-gating per provider.

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 description opens with a specific verb and resource ('Read ... clicks, impressions, CTR, average position') and enumerates the returned metrics, data sources (Google Search Console, Bing Webmaster Tools), and views (previous-period totals, daily trends, top queries and pages). An agent can distinguish this from `get_analytics`, `get_current_visitors`, and `get_blog` without opening a schema.

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

Usage Guidelines4/5

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

It clearly states prerequisites (an existing connection on the Analytics page, an eligible analytics/API plan) and the 30-day default, which tells the agent when this tool is callable at all. It does not explicitly contrast with sibling tools like `get_analytics` or say when NOT to use it, so it falls short of full when/when-not guidance.

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