Skip to main content
Glama
Sign In

Bing Webmaster Tools MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Bing Webmaster Execute Action

execute_action
Destructive

Execute Bing Webmaster Tools action (Step 3 (FINAL) of workflow).

REQUIRED: Complete these steps first using query_contexts:

  1. request='accounts' - Get workspace_id, brand_id AND available_actions

  2. request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] - Get detailed body structure for specific action(s) using actions from available_actions

IMPORTANT: Always call step 2 to see the exact body structure before executing.

Rely on info from steps 1-2 to construct the action body. Follow the schema exactly.

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": {
      "body": "<body>"
    },
    "name": "execute_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the risk profile is covered structurally; the description's added value is the hard sequential dependency and the fact that the payload cannot be authored without a prior discovery call. It does not describe consequences, reversibility, or side effects on the Bing account, which is the remaining gap.

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 label ('Step 3 (FINAL) of workflow') followed by a numbered, scannable prerequisite list; every line is actionable. Slight redundancy from stacked 'REQUIRED'/'IMPORTANT' emphasis and the literal 'xxxxxx' placeholders costs a point.

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 destructive, free-form-payload write tool with an output schema present, the description supplies everything needed to invoke it correctly: preconditions, ordering, and the source of truth for the body. Only the post-execution effect on the account is left implicit.

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 0% and the single 'body' param is an unconstrained free-form object, so the schema alone tells the agent nothing. The description compensates as well as possible by directing it to request='actions_details' with the chosen action IDs to obtain the exact body structure and to follow that schema exactly.

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 concrete verb and resource ('Execute Bing Webmaster Tools action') and frames it as the terminal step of a specific workflow, which separates it cleanly from the query_* siblings. The action itself is left opaque by design (it is discovered at runtime), so an agent knows what class of operation this is but not the specific operation until step 1.

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

Usage Guidelines5/5

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

It explicitly names the prerequisite tool (query_contexts), enumerates the two required calls with their exact request values, and states a hard exclusion ('IMPORTANT: Always call step 2 ... before executing'). There is no ambiguity about ordering or alternatives.

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

All Bing Webmaster Tools MCP by InsightfulPipe toolsInspect
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