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

Bing Webmaster Tools MCP Server

by zizzfizzix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

add_site_roles

Assign a user to your Bing Webmaster site with administrator or read-only permissions using their email and an authentication code.

Instructions

Delegate site access to a user.

Args: site_url: The URL of your site delegated_url: The URL being delegated user_email: The email of the user to delegate access to authentication_code: The authentication code is_administrator: Whether the user should have administrator privileges is_read_only: Whether the user should have read-only access

Raises: BingWebmasterError: If the role assignment fails

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>",
      "delegated_url": "<delegated_url>",
      "user_email": "<user_email>",
      "authentication_code": "<authentication_code>",
      "is_administrator": "<is_administrator>",
      "is_read_only": "<is_read_only>"
    },
    "name": "add_site_roles"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_urlYes
user_emailYes
is_read_onlyYes
delegated_urlYes
is_administratorYes
authentication_codeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

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",
-  "delegated_url",
-  "user_email",
-  "authentication_code",
-  "is_administrator",
-  "is_read_only"
-]New value: +[
+  "site_url",
+  "delegated_url",
+  "user_email",
+  "authentication_code",
+  "is_administrator",
+  "is_read_only"
+]
  2. Changed1 schema field changedv1.0.0
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "result": {
+      "title": "Result",
+      "type": "null"
+    }
+  },
+  "required": [
+    "result"
+  ],
+  "title": "add_site_rolesOutput",
+  "type": "object"
+}
  3. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description must disclose side effects. It only mentions that a BingWebmasterError is raised on failure knthu and that it delegates access. It fails to explain whether existing roles are overwritten, whether both admin and read-only can be true, or what happens on partial failure.

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 docstring is compact, front-loads the purpose, and separates parameter definitions from a Raises section. It earns a solid score for brevity and readability.

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 description covers the basic action, all six parameters, and the error type. However, it omits context about the semantics of delegating (e.g., whether roles are additive, how the delegated_url relates to site_url, and whether both boolean flags can be true). An output schema exists, so return values need not be described.

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?

The Arg list gives a one-line gloss for each parameter (e.g., 'user_email: The email of the user to delegate access to'), but these largely restate the parameter names and don't clarify ambiguous fields like delegated_url or the relationship between is_administrator and is_read_only. Schema descriptions are absent, so the description partially compensates but remains shallow.

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 line, 'Delegate site access to a user,' clearly identifies the action and target. It is specific enough to convey the tool's primary function, though it does not distinguish it from related tools like remove_site_roles.

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?

No guidance is provided on when to use this tool versus sibling tools (e.g., get_site_roles, remove_site_roles). The description does not explain prerequisites, typical scenarios, or how roles interact.

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