Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Get Link Counts

bing_webmaster_get_link_counts
Read-only

List site pages with inbound link counts, one page at a time, to identify which pages earn external links; use the URL links tool to inspect backlinks and anchor text for one page.

Instructions

The site's pages that have inbound links from other sites, with how many each has, one page of results at a time (page 0 first; the answer gives total_pages and next_page). For who links to one page, and with what anchor text, use bing_webmaster_get_url_links.

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": "<site>"
    },
    "name": "bing_webmaster_get_link_counts"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResult page, 0-based. Each answer says total_pages and next_page. Defaults to 0.
siteYesThe site, e.g. "example.com" or "https://www.example.com/". Matched against the sites this API key reaches (bing_webmaster_list_sites), tolerating a missing scheme, www. or trailing slash; an ambiguous or unknown site is refused with the list of accessible ones.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds genuinely useful behavior beyond them — pagination ordering (page 0 first) and the returned pagination fields (total_pages, next_page) — but says nothing about result ordering, page size, or how freshness/coverage varies with the API key's reachable sites.

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?

Two sentences, both earning their place: the first front-loads what is returned and how it is paginated, the second handles sibling routing. No filler or redundant restatement of the title.

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?

With no output schema, the description usefully discloses the key response fields and the paging protocol, and the site parameter's normalization behavior is covered in the schema. Minor gaps remain around result ordering and per-page size, which an agent would want when iterating pages.

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%, so both parameters are already documented, including the 0-based page default and the site matching/normalization rules. The description's pagination notes largely restate the schema's page description, adding no new syntax or semantics, so the baseline of 3 applies.

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 names the exact resource and shape of the result: the site's pages with inbound links from other sites, plus a per-page count, delivered one page at a time. It also explicitly contrasts with bing_webmaster_get_url_links, so an agent can distinguish this from the drill-down sibling without opening either schema.

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?

It gives an explicit routing rule: use this tool for per-page inbound link totals, and use bing_webmaster_get_url_links when the question is who links to one page and with what anchor text. That is a concrete when-to-use-this / when-to-use-the-alternative statement rather than implied context.

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