SEO GSC Wizard MCP

Bing inbound link counts

get_bing_link_counts

Read-only

Use this when the user asks which of their URLs have the most backlinks according to Bing. Inbound (backlink) counts per URL that Bing Webmaster Tools has recorded for a property, one page of Bing's results at a time, in Bing's order: most inbound links first. Pass page to paginate, though page 0 usually holds every row: despite its name, totalPages is the number of linked URLs Bing reports, not a count of result pages. Not for Google link data, which no tool here reads. Returns notConfigured: true when no Bing Webmaster API key is set up for the property.

Input Schema

Name	Required	Description
`page`	No	Zero-based page index for pagination (default 0).
`limit`	No	Max link rows to return from the page (default 100). Page 0 usually holds every linked URL Bing reports, which can be far more than 100; lower this to keep the payload small.
`siteUrl`	Yes

Output Schema

Name	Required	Description
`hint`	No
`page`	No
`links`	No
`range`	No
`thenBy`	No
`listKey`	No	Name of the top-level field that holds the rows sortedBy describes.
`siteUrl`	No
`warning`	No
`nextStep`	No
`ordering`	No
`rowCount`	No
`sortedBy`	No
`dateBasis`	No
`sortOrder`	No
`thenOrder`	No
`truncated`	No
`dataSource`	No
`totalPages`	No	The number of linked URLs Bing reports, not a count of result pages.
`bingSiteUrl`	No
`partialDays`	No	Requested days among Bing's newest (provisional) or after latestDataDate (missing, not zero), up to today.
`completeness`	No
`emptyBecause`	No
`methodLimits`	No
`pageRowCount`	No
`notConfigured`	No
`latestDataDate`	No	Newest date with a row in everything Bing sent for this call, before the window filter.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 28, 2026

addedOutput schema / properties / completeness

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / dateBasis

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / latestDataDate

Added value: +{
+  "$ref": "#/properties/siteUrl",
+  "description": "Newest date with a row in everything Bing sent for this call, before the window filter."
+}

addedOutput schema / properties / listKey

Added value: +{
+  "$ref": "#/properties/siteUrl",
+  "description": "Name of the top-level field that holds the rows sortedBy describes."
+}

addedOutput schema / properties / partialDays

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Requested days among Bing's newest (provisional) or after latestDataDate (missing, not zero), up to today."
+}

addedOutput schema / properties / warning

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

Changed13 schema fields changedOct 18, 2026

changedInput schema / properties / limit / description

Previous value: -"Max link rows to return from the page (default 100). Bing returns up to ~100 rows per page but large properties can exceed that; lower this to keep the payload small."New value: +"Max link rows to return from the page (default 100). Page 0 usually holds every linked URL Bing reports, which can be far more than 100; lower this to keep the payload small."

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / emptyBecause

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

changedOutput schema / properties / links / items / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / methodLimits

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / nextStep

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / ordering

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": {
+        "additionalProperties": true,
+        "properties": {
+          "sortOrder": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "sortedBy": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "thenBy": {
+            "$ref": "#/properties/siteUrl"
+          },
+          "thenOrder": {
+            "$ref": "#/properties/siteUrl"
+          }
+        },
+        "type": "object"
+      },
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

changedOutput schema / properties / range / anyOf

Previous value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "days": {
-        "type": [
-          "number",
-          "null"
-        ]
-      },
-      "endDate": {
-        "$ref": "#/properties/siteUrl"
-      },
-      "startDate": {
-        "$ref": "#/properties/siteUrl"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": true,
+    "properties": {
+      "days": {
+        "type": [
+          "number",
+          "null"
+        ]
+      },
+      "endDate": {
+        "$ref": "#/properties/siteUrl"
+      },
+      "startDate": {
+        "$ref": "#/properties/siteUrl"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]

addedOutput schema / properties / sortOrder

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / sortedBy

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / thenBy

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / thenOrder

Added value: +{
+  "$ref": "#/properties/siteUrl"
+}

addedOutput schema / properties / totalPages / description

Added value: +"The number of linked URLs Bing reports, not a count of result pages."

First observedOct 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds behavior beyond that: results come in Bing's order (most inbound links first), pagination works per Bing's result page, and it returns notConfigured: true when no Bing Webmaster API key exists — useful operational context for an open-world call. It does not mention rate limits or latency, which keeps it off 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the use case, and every sentence carries information: ordering, pagination caveat, totalPages clarification, Google exclusion, notConfigured behavior. The middle clauses are dense run-ons ('though page 0 usually holds every row: despite its name, totalPages is...'), which slightly hurts scanability but no sentence is filler.

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 an output schema present, return values needn't be re-explained, and the description still flags the notable notConfigured shape. Annotations cover the mutation/safety profile. The only real gap for an agent is how siteUrl should be formatted (full URL vs host), which is undocumented in both places.

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 coverage is 67%; `limit` is fully documented in the schema and `page` is described there too. The description adds real nuance on `page` ('page 0 usually holds every row') and explains the misleading totalPages value. `siteUrl` has no description in either schema or description (format expectations unspecified), which caps this at 4.

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?

States a specific verb and resource ('Inbound (backlink) counts per URL that Bing Webmaster Tools has recorded for a property') and scopes it to 'which of their URLs have the most backlinks according to Bing'. It is clearly distinguishable from the many Google/GSC siblings, and the exclusion of Google link data removes ambiguity about which dataset is returned.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Opens with an explicit use trigger ('Use this when the user asks which of their URLs have the most backlinks according to Bing') and names an exclusion ('Not for Google link data, which no tool here reads'). It stops short of pointing to any alternative tool for related link questions, but for this dataset there is no Bing sibling to route to, so the gap is small.

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

All SEO GSC Wizard MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?