Skip to main content
Glama
mcp-bing-webmaster

mcp-bing-webmaster

by mgcrea

Bing Webmaster: Get URL Links

bing_webmaster_get_url_links
Read-only

Fetches external pages linking to a specific URL on a site, including anchor text, and returns paginated inbound-link results.

Instructions

The external pages linking to one page of the site, with their anchor text, one page of results at a time (page 0 first; the answer gives total_pages and next_page).

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>",
      "url": "<url>"
    },
    "name": "bing_webmaster_get_url_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe linked-to page, as bing_webmaster_get_link_counts reports it — an absolute URL, e.g. "https://example.com/pricing".
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

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the description's contribution is the pagination contract: results come back one page at a time, page 0 is the start, and each response carries total_pages and next_page. That is real behavioral context not present in structured fields, especially valuable since there is no output schema. Missing details such as result ordering or approximate result size keep it from a 5.

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?

A single sentence with zero filler; the resource and the pagination behavior are front-loaded together, and nothing is repeated between the description and itself.

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 three-parameter read tool with full schema coverage and no output schema, the definition supplies what an agent needs: what is returned (linking pages plus anchor text) and how paging works. The only gap is explicit differentiation from the count-oriented sibling, which the schema hints at but the description does not state.

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 the schema already explains site, url, and page in detail, including the link_counts cross-reference and the 0-based default. The description only restates the page-indexing behavior, adding little beyond what the schema provides. Baseline 3 applies.

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 resource — the external pages linking to a single page, plus their anchor text — which is clearly distinct from the aggregate counts a sibling like bing_webmaster_get_link_counts would give. It is phrased as a noun fragment rather than a verb+resource statement, and it does not explicitly name the sibling it differs from, so it falls short of a 5.

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: the agent can infer this is the tool for per-link detail rather than counts, and the parenthetical 'page 0 first' gives pagination procedure. But there is no explicit when-to-use/when-not guidance and no named alternative tool to route to, so it stays at minimum-viable.

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