Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_connected_pages

Retrieve pages connected to a site by providing its URL, with pagination support via limit and offset parameters.

Instructions

Get a list of pages connected to the site.

Args: site_url: The URL of the site

Returns: List[ConnectedSite]: List of connected sites

Raises: BingWebmasterError: If connected pages cannot be retrieved

Returns at most limit rows (default 50, max 500). When the result reports a next_offset, call again with offset=next_offset to get more rows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of rows to return.
offsetNoIndex of the first row.
site_urlYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.2.0
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 50,
+  "description": "Maximum number of rows to return.",
+  "maximum": 500,
+  "minimum": 1,
+  "title": "Limit",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Index of the first row.",
+  "minimum": 0,
+  "title": "Offset",
+  "type": "integer"
+}
    • removedInput schema / properties / self
      Removed value: -{
-  "title": "self",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "self",
-  "site_url"
-]New value: +[
+  "site_url"
+]
  2. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$defs": {
+    "ConnectedSite": {
+      "properties": {
+        "SubmissionDate": {
+          "format": "date-time",
+          "title": "Submissiondate",
+          "type": "string"
+        },
+        "Url": {
+          "title": "Url",
+          "type": "string"
+        },
+        "VerificationStatus": {
+          "title": "Verificationstatus",
+          "type": "string"
+        },
+        "VerificationStatusDetails": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "title": "Verificationstatusdetails"
+        },
+        "VerifiedDate": {
+          "anyOf": [
+            {
+              "format": "date-time",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "title": "Verifieddate"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "Url",
+        "VerificationStatus",
+        "VerificationStatusDetails",
+        "VerifiedDate",
+        "SubmissionDate"
+      ],
+      "title": "ConnectedSite",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/ConnectedSite"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_connected_pagesOutput",
+  "type": "object"
+}
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses the limit behavior, default/max limits, the next_offset continuation pattern, and that BingWebmasterError is raised on failure. This goes beyond a bare getter, though it does not cover prerequisite or authentication conditions.

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 and front-loaded: a one-sentence summary, a concise args/returns/raises docstring, and a short pagination note. Every sentence contributes, and there is no 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?

For a paginated read operation, the description gives the required site_url, optional limit/offset, pagination pattern, and error behavior, while the output schema covers the return shape. It is slightly incomplete about what 'connected pages' means and what makes a site eligible, but the core calling contract is fully specified.

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%, and the description compensates by defining the otherwise undocumented site_url parameter ('The URL of the site'). It also explains how offset relates to pagination, adding meaning beyond the schema's 'Index of the first row.' The limit default/max is redundant with the schema, but the missing parameter is covered.

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 opening sentence names a specific operation and resource: 'Get a list of pages connected to the site.' It clearly signals a read operation and is distinguishable from write-oriented siblings like add_connected_page. However, it does not explicitly differentiate itself from similar getters, and the return type 'List[ConnectedSite]' introduces minor pages-vs-sites ambiguity.

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?

The description implies use whenever connected pages are needed and gives clear pagination guidance ('call again with offset=next_offset'). However, it provides no when-not-to-use conditions or alternatives, so usage is mostly implied rather than explicitly scoped against sibling tools.

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