Skip to main content
Glama
Sign In
Bing Webmaster Tools MCP Server

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_url_links

Fetch inbound links pointing to a specific URL to analyze backlinks and referral traffic. Specify site URL and target link, with optional page number for paginated results.

Instructions

Retrieve inbound links for a specific URL.

Args: site_url: The URL of the site link: The specific URL to get inbound links for page: The page number of results to retrieve

Returns: LinkDetails: Details about inbound links

Raises: BingWebmasterError: If link details 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>",
      "link": "<link>"
    },
    "name": "get_url_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
linkYes
pageNo
site_urlYes

Output Schema

NameRequiredDescriptionDefault
DetailsYes
TotalPagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.0
    • removedInput schema / properties / self
      Removed value: -{
-  "title": "self",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "self",
-  "site_url",
-  "link"
-]New value: +[
+  "site_url",
+  "link"
+]
  2. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "LinkDetail": {
+      "properties": {
+        "AnchorText": {
+          "title": "Anchortext",
+          "type": "string"
+        },
+        "Url": {
+          "title": "Url",
+          "type": "string"
+        }
+      },
+      "required": [
+        "AnchorText",
+        "Url"
+      ],
+      "title": "LinkDetail",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "Details": {
+      "items": {
+        "$ref": "#/$defs/LinkDetail"
+      },
+      "title": "Details",
+      "type": "array"
+    },
+    "TotalPages": {
+      "title": "Totalpages",
+      "type": "integer"
+    }
+  },
+  "required": [
+    "Details",
+    "TotalPages"
+  ],
+  "title": "LinkDetails",
+  "type": "object"
+}
  3. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations to lean on, the description carries the full burden. It does disclose read-only retrieval semantics, pagination through the page argument, and a possible error via 'Raises: BingWebmasterError', which adds some behavioral context, but it does not mention permissions, rate limits, or result-page behavior.

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 compact, clearly organized into Args, Returns, and Raises sections, and contains no filler. Every sentence contributes useful information.

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 simple read operation with an output schema and no nested objects, the description covers the essential invocation details: parameters, return type, and error condition. It is complete enough for an agent to call it correctly, though it lacks usage guidance.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate. The Args section provides a meaningful one-line explanation for each parameter, especially clarifying that 'link' is the URL whose inbound links are being retrieved.

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 verb and resource: 'Retrieve inbound links for a specific URL.' It is distinct enough from most siblings, though it does not explicitly contrast itself with similar tools like get_link_counts or get_url_info.

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 guidance about when to use this tool versus alternatives such as get_link_counts or get_url_info. The description gives the operation but not the decision context.

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