Skip to main content
Glama
zizzfizzix

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_site_roles

Retrieve all role assignments for a site, optionally including subdomains, to manage user permissions and access control.

Instructions

Get all roles assigned for a specific site.

Args: site_url: The URL of the site include_all_subdomains: Whether to include roles for all subdomains

Returns: List[SiteRole]: List of role assignments for the site

Raises: BingWebmasterError: If the roles 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
include_all_subdomainsNo

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": {
+    "SiteRole": {
+      "properties": {
+        "Date": {
+          "format": "date-time",
+          "title": "Date",
+          "type": "string"
+        },
+        "DelegatedCode": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Delegatedcode"
+        },
+        "DelegatedCodeOwnerEmail": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Delegatedcodeowneremail"
+        },
+        "DelegatorEmail": {
+          "anyOf": [
+            {
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ],
+          "default": null,
+          "title": "Delegatoremail"
+        },
+        "Email": {
+          "title": "Email",
+          "type": "string"
+        },
+        "Expired": {
+          "title": "Expired",
+          "type": "boolean"
+        },
+        "Role": {
+          "$ref": "#/$defs/UserRole"
+        },
+        "Site": {
+          "title": "Site",
+          "type": "string"
+        },
+        "VerificationSite": {
+          "title": "Verificationsite",
+          "type": "string"
+        },
+        "__type": {
+          "title": "Type",
+          "type": "string"
+        }
+      },
+      "required": [
+        "__type",
+        "Date",
+        "Email",
+        "Expired",
+        "Role",
+        "Site",
+        "VerificationSite"
+      ],
+      "title": "SiteRole",
+      "type": "object"
+    },
+    "UserRole": {
+      "enum": [
+        0,
+        1,
+        2
+      ],
+      "title": "UserRole",
+      "type": "integer"
+    }
+  },
+  "properties": {
+    "result": {
+      "items": {
+        "$ref": "#/$defs/SiteRole"
+      },
+      "title": "Result",
+      "type": "array"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "get_site_rolesOutput",
+  "type": "object"
+}
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses pagination semantics (limit default/max, next_offset loop), the error type (BingWebmasterError), and the return type. This goes beyond the schema and provides useful behavioral context.

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?

Well-structured with clear sections for purpose, args, returns, raises, and pagination. Each sentence earns its place, though the return type is also present in the output schema, making that part slightly redundant.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, the description covers the tool's purpose, all parameters (via Args and the pagination note), return type, error behavior, and the pagination loop. An agent has enough information to select and invoke the tool correctly.

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 50% and only covers limit/offset. The description's Args section adds meaning to site_url and include_all_subdomains, compensating for the gap. It also adds pagination context to limit/offset, which the schema does not fully convey.

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 (Get), resource (roles), and scope (specific site). Clearly distinguishes from sibling add_site_roles/remove_site_role as a read operation.

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?

Does not explicitly state when to use this tool vs alternatives. The read-only nature is implied by the verb, but there is no mention of sibling add_site_roles/remove_site_role or any exclusion context. For a simple getter the context is reasonable, but guidance is only implied.

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