Skip to main content
Glama
Sign In
mcp-server-bing-webmaster

mcp-server-bing-webmaster

by isiahw1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_connected_pages

Retrieve pages linking to your website to analyze backlink profiles and monitor referral traffic sources.

Instructions

Get list of connected pages that link to your site.

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

Input Schema

NameRequiredDescriptionDefault
site_urlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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. It conveys that the tool performs a read-only list retrieval scoped to pages linking to the user's site, which is minimally transparent. However, it does not explain what 'connected' means, pagination behavior, or any data source limitations.

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?

The description is a single front-loaded sentence with no filler. Every word earns its place, and the core action and target resource are immediately clear.

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?

The tool is simple with one required parameter and an output schema, so basic invocation is possible. However, the description leaves 'connected pages' ambiguous and provides no context for selecting this tool among 33 similar link- and page-oriented siblings.

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?

The input schema has only site_url with no description and 0% schema description coverage, so the description must compensate. It implies site_url refers to 'your site', but it does not clarify expected format, whether protocol is needed, or how the value relates to the returned connected pages.

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 uses a clear verb ('Get') and names a specific resource ('connected pages that link to your site'). However, it does not explicitly distinguish this from similar siblings like get_url_links or get_link_counts, so the term 'connected pages' remains somewhat ambiguous.

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 choose this tool over its many siblings. The description states only what the tool does, with no context about when it is appropriate or when an alternative like get_url_links should be used.

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