Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_active_page_preview_blocks

Retrieve active page preview blocks for a site. Paginate with limit and offset to get all results, handling next_offset for larger datasets.

Instructions

Get active page preview blocks for a site.

Args: site_url: The URL of the site

Returns: List[PagePreview]: List of active page preview blocks

Raises: BingWebmasterError: If preview blocks 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": {
+    "BlockReason": {
+      "enum": [
+        1,
+        2,
+        3,
+        4
+      ],
+      "title": "BlockReason",
+      "type": "integer"
+    },
+    "PagePreview": {
+      "properties": {
+        "BlockDate": {
+          "anyOf": [
+            {
+              "format": "date-time",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Blockdate"
+        },
+        "BlockReason": {
+          "$ref": "#/$defs/BlockReason"
+        },
+        "Url": {
+          "title": "Url",
+          "type": "string"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "Url",
+        "BlockReason"
+      ],
+      "title": "PagePreview",
+      "type": "object"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/PagePreview"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_active_page_preview_blocksOutput",
+  "type": "object"
+}
  3. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses pagination behavior (limit, offset, next_offset) and error behavior (BingWebmasterError), which is useful. However, it does not mention whether this is a read-only operation, rate limits, or what 'active' means in terms of filtering. The pagination and error details add value beyond the schema.

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?

The description is concise and front-loaded with the core purpose. The Args/Returns/Raises structure is clear and scannable. The pagination note is placed at the end, which is appropriate. No wasted words, though the format could be slightly more compact.

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 has an output schema (List[PagePreview]) and 3 parameters, so the description doesn't need to explain return values in detail. However, with no annotations, the description should disclose more about the operation's safety (read-only vs. mutating) and any prerequisites. The pagination and error details are good, but the lack of usage context relative to siblings leaves a gap.

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 67%, with limit and offset already described in the schema. The description adds the site_url parameter context ('The URL of the site') but that is minimal. The pagination explanation in the description adds meaning to limit and offset beyond the schema's basic descriptions, but it doesn't fully compensate for the missing site_url schema description.

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 states a specific verb and resource: 'Get active page preview blocks for a site.' This clearly identifies the operation and the resource. It is distinguishable from siblings like add_page_preview_block and remove_page_preview_block, though it doesn't explicitly name them.

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 usage by stating it retrieves active page preview blocks for a site, and the pagination instructions provide context for repeated calls. However, it does not explicitly state when to use this tool versus alternatives like get_deep_link_blocks or add_page_preview_block, nor does it mention any prerequisites.

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