Skip to main content
Glama

bing_get_query_stats

Retrieve Bing search query statistics for a site to analyze keyword impressions, clicks, and positions; data updates weekly.

Instructions

Get search query (keyword) statistics for a site from Bing. Shows impressions, clicks, and positions. Data updates weekly.

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": {
      "siteUrl": "<siteUrl>"
    },
    "name": "bing_get_query_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteUrlYesThe site URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the return payload (impressions, clicks, positions) plus a freshness cadence (updates weekly). It does not cover permissions, history depth, pagination, or whether results are aggregated, so behavioral disclosure remains partial for a read tool.

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

Conciseness5/5

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

Three short sentences, zero filler: purpose first, return fields second, refresh cadence last. Every sentence adds information an agent can use.

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

Completeness4/5

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

For a one-parameter read-only retrieval tool with no output schema, the description covers what the tool does, what it returns, and how fresh the data is. Only a note on aggregation level or historical range is missing, which is a minor gap.

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

Parameters3/5

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

Schema description coverage is 100% for the single siteUrl parameter, so the schema already documents the input. The description reinforces that data is scoped to 'a site' but adds no format or validation detail beyond the schema, making the baseline 3 appropriate.

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

Purpose4/5

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

The description names a specific verb and resource (get search query/keyword statistics for a site from Bing) and lists the exact metrics returned (impressions, clicks, positions). This distinguishes it reasonably well from siblings like bing_get_page_stats or bing_get_crawl_stats, though it never explicitly contrasts with them.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for keyword-level performance data, but there is no statement of when to prefer it over bing_get_page_stats or bing_get_traffic, and no prerequisites or exclusions are given.

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