Skip to main content
Glama
Sign In

Bing Webmaster Tools MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Bing Webmaster Data Query

query_data
Read-only

Query Bing Webmaster Tools data (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 querying.

Rely on info from steps 1-2 to construct the query 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": "query_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

readOnlyHint and openWorldHint already declare the safety profile, so the description needn't restate that. It adds real behavioral context annotations cannot: this call is gated on two prior query_contexts calls and will be constructed wrongly without them. It stops short of saying what happens on schema-violating bodies or what the response shape is (deferred to the output schema).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The prerequisite list is well front-loaded, but the point is made three times: "Step 3 (FINAL)", "IMPORTANT: Always call step 2 to see the exact body structure", and "Rely on info from steps 1-2 to construct the query body". One of these sentences could be dropped without losing information.

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 single free-form parameter with an output schema present, the critical missing piece is how to build the body, and the description routes that through a concrete, checkable procedure. An agent following it can call correctly; it is only the failure/latency behavior and error cases that go unaddressed.

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 coverage is 0% and `body` is an untyped free-form object with additionalProperties: true, so the schema conveys nothing. The description's only compensation is a deferral: fetch the exact structure via query_contexts step 2. That is a useful pointer but gives no direct semantics for any field the agent will write.

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?

States a specific verb and resource ("Query Bing Webmaster Tools data") and pins its position as the final step of a three-step workflow, which is what separates it from sibling query_contexts. It never says what kinds of data are queryable or what entity the `body` targets, so the resource remains abstract.

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

Usage Guidelines4/5

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

Explicitly names the prerequisite tool and the two exact requests ('accounts', 'actions_details') with the arguments to pass, and mandates step 2 before querying. It does not distinguish itself from execute_action (presumably the mutation path), leaving that routing decision to the agent.

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