Skip to main content
Glama
Sign In
mcp-server-bwt

mcp-server-bwt

by agalliani
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_rank_and_traffic_stats

Get ranking and traffic statistics for a site to assess its search visibility and performance.

Instructions

Get ranking and traffic statistics for a site.

Args: site_url: The URL of the site

Returns: List[RankAndTrafficStats]: List of ranking and traffic statistics

Raises: BingWebmasterError: If statistics cannot be retrieved

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": {
      "site_url": "<site_url>"
    },
    "name": "get_rank_and_traffic_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

There are no annotations, so the description carries the burden. It does disclose a specific failure mode (raises BingWebmasterError) and that it returns a list, which adds some transparency. However, it does not mention side effects, permissions, rate limits, or data freshness.

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?

The structure is clean, front-loaded, and compact: summary, Args, Returns, Raises. It is not verbose, though the Returns section largely duplicates what an output schema would provide.

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?

For a one-parameter read-only lookup, it covers the essentials: parameter, return type, and an error condition. However, it lacks any usage context or clarification of scope relative to sibling stats tools, and with no annotations it could be more explicit about expected behavior.

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

Parameters2/5

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

Schema coverage is 0%, but the description only restates the obvious: site_url is 'The URL of the site.' It does not clarify required format (e.g., with or without protocol), whether the site must be a verified property, or any constraints on the parameter.

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 clearly states a specific action and resource: 'Get ranking and traffic statistics for a site.' It is more than a restatement of the name)Skip, though it does not explicitly differentiate itself from similar sibling tools like get_query_stats or get_page_stats.

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?

No guidance is given about when to use this tool versus the many sibling statistics/reporting tools, nor about prerequisites or expected context. It only describes what the function does and returns.

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

Deploy Server

Other Tools