Skip to main content
Glama
Sign In

Bing Webmaster Tools MCP by InsightfulPipe

by com.insightfulpipe
OverviewDiscussionsAdmin

Server Details

Hosted Bing Webmaster Tools MCP server, with each action switched on or off per account.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
OAuth
Works in Glama
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
Insightful-Pipe/bing-webmaster-mcp-server
GitHub Stars
0
ChatGPT
–
Claude
–

TDQS

A3.6/5.0

Scored across 4 tools

Disambiguation2/5

execute_action and query_data are described almost identically — both are labeled 'Step 3 (FINAL) of workflow', both require the same query_contexts prerequisites, and both build a body from available_actions. An agent cannot reliably tell which one to call, so selection is guesswork. Only prompts_menu is clearly distinct.

Naming Consistency4/5

Three of four names follow a verb_noun pattern (execute_action, query_contexts, query_data), which is predictable and readable. prompts_menu breaks the pattern as a noun-first name, a minor but noticeable deviation.

Tool Count3/5

Four tools is thin for a webmaster-tools domain, and only two of them actually do work; the real surface is hidden behind an opaque dynamic action list. The indirection keeps the count small but leaves the set feeling under-specified rather than well-scoped.

Completeness3/5

Read/execute capability is nominally unified through execute_action, and query_contexts provides discovery, so basic workflows are reachable. However, coverage depends entirely on an opaque available_actions list, and there is no distinct surface for site management, URL submission, or verification tasks that agents would expect from Bing Webmaster Tools.

Available Tools

4 tools
execute_actionBing Webmaster Execute ActionA
Destructive
Inspect

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.

Inputs: body (required). Returns: object

prompts_menuBing Webmaster PromptsA
Read-only
Inspect

Browse the Bing Webmaster Tools prompt catalog.

  1. request='menu' – List public/system prompts (optionally pass workspace_id + prompt_type).

  2. request='prompt_details' – Fetch prompt body by prompt_id. Set is_custom=True + workspace_id for workspace prompts.

Inputs: request (required), is_custom, prompt_id, prompt_type, +1 more. Returns: object

query_contextsBing Webmaster Setup HelperA
Read-only
Inspect

Helper for planning InsightfulPipe Bing Webmaster Tools data queries.

Step 1: request='accounts' – Retrieve workspace_id, brand_id, other source metadata, AND available_actions (all tables you can query).

Step 2: request='actions_details' with actions=['xxxxxx', 'xxxxxx', 'xxxxxx'] – REQUIRED before querying. Replace with actions from available_actions to get the exact request body, required identifiers, fields, time ranges, and notes for each action.

Optional: request='available_actions' – Standalone call to list all available tables/actions (already included in accounts response).

Optional: request='brands' with brand_id + workspace_id to pull brand guidelines.

Inputs: request (required), actions, brand_id, platform, +1 more. Returns: object

query_dataBing Webmaster Data QueryA
Read-only
Inspect

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.

Inputs: body (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • bing-webmaster-mcp

      R1tom
      A
      license
      B
      quality
      C
      maintenance
      MCP server for Bing Webmaster Tools: search performance, traffic trends, crawl health, URL index status, sitemaps, backlinks, keyword research and URL submission including IndexNow.
      10
      MIT

    • bing-webmaster-mcp

      ismaelJimenez
      A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to manage Bing Webmaster Tools data, including search performance, sitemaps, URL submission, IndexNow pings, crawl diagnostics, keyword research, and backlinks.
      14
      31 npm
      MIT

    • Bing Webmaster Tools MCP

      zizzfizzix
      A
      license
      C
      quality
      B
      maintenance
      A Model Context Protocol server that enables AI assistants like Claude to interact with Bing Webmaster Tools API, allowing users to manage sites, submit URLs for indexing, analyze traffic, and access other webmaster tools through natural language.
      62
      54 PyPI
      7
      MIT
    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