Skip to main content
Glama
Sign In

mowteng

by app.mowteng
OverviewDiscussionsAdmin

Bing search performance

bing_search_stats
Read-only

Bing clicks, impressions and average position per query or per page, totalled over the weeks Bing returns (the period is in the result; Bing reports weekly). Position is in Bing's own unit. Paged with offset and limit.

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_search_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoOrder by clicks or impressions, highest first. Defaults to clicks.clicks
limitNoMaximum items to return (1-500). Defaults to 50.
offsetNoNumber of items to skip, for paging. Defaults to 0.
siteUrlYesBing site URL exactly as bing_list_sites returns it, e.g. https://example.com/
containsNoOnly keys containing this text, case-insensitive
dimensionNoGroup by search query or by page. Defaults to query.query

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (read-only, non-destructive, closed-world), and the description adds real behavioral context on top: totals span whatever weeks Bing returns, the period appears in the result, reporting is weekly, and position uses Bing's own unit rather than Google's. It does not describe the result field names, but the caveats given are exactly the non-obvious ones.

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?

Three tight sentences with the metric definition front-loaded, followed by the weekly-period caveat, the position-unit caveat and paging. No filler; phrasing is slightly compressed ('totalled over the weeks Bing returns') but still parseable.

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

Completeness3/5

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

With no output schema and six parameters, the description should say more about the returned structure than 'the period is in the result'. It is adequate for a read-only analytics call but leaves the result shape and the sort/contains behavior to the schema alone.

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 coverage is 100%, so sort, limit, offset, contains, dimension and siteUrl are already fully documented in the schema. The description only restates paging ('Paged with offset and limit') and the dimension choice, adding no syntax or format detail beyond the schema.

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 pair – Bing clicks, impressions and average position – plus the two grouping modes (per query or per page). 'Bing' distinguishes it from the Google/Yandex analytics siblings, though no sibling is named explicitly.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no routing to alternatives such as gsc_search_analytics or yandex_search_queries, which cover analogous data for other engines. The reader must infer the choice from the word 'Bing'.

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

All mowteng toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources