CorpusIQ

Bing Webmaster Connector

bing_webmaster_connector

Read-onlyIdempotent

Bing Webmaster Tools (Microsoft) organic-search data for a verified site: rank & traffic stats (impressions/clicks over time), top search queries with positions, per-URL index & traffic detail, crawl statistics (crawled pages, in-index, errors, status codes), and inbound link counts. Use for Bing SEO reporting, organic-search visibility, keyword/query analysis, crawl health, and backlink volume. Auth: OAuth 2.0. When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`action`	Yes	get_sites: List the sites the connected Bing Webmaster user has verified. Call this first to discover the siteUrl values the other \| get_rank_and_traffic: Get the Bing organic rank & traffic time series for a verified site: daily impressions and clicks, plus totals over the \| get_query_stats: Get the top Bing search queries driving impressions and clicks to a verified site, with average impression/click positio \| get_url_traffic: Get index + traffic detail for a single page on a verified site: clicks, impressions, indexed status, last-crawled date, \| get_crawl_stats: Get the Bing crawl statistics time series for a verified site: crawled pages, in-index count, inbound links, crawl error \| get_link_counts: Get inbound link counts per page for a verified site (the Bing inbound-link profile). Use for off-page SEO, backlink vol
`params`	No	Action-specific parameters. get_sites: none \| get_rank_and_traffic: {site_url: string} \| get_query_stats: {site_url: string} \| get_url_traffic: {site_url: string, url: string} \| get_crawl_stats: {site_url: string} \| get_link_counts: {site_url: string, page?: integer}

Schema Changelog

Changes observed during successful MCP inspections.

AddedJun 18, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, covering the core safety profile. The description adds the OAuth 2.0 auth requirement and the need for a verified site, which is useful. It does not disclose rate limits, error behavior, or output format details beyond annotations, hence a 3.

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

Conciseness2/5

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

The description is overly long and includes extensive instructions about chart_render, provenance tokens, attribution footers, and a data accuracy contract that are not specific to invoking this tool. These dilute the core purpose and make it less concise.

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?

Given the fully covered schema and annotations, the description provides an adequate overview of the data returned and auth context. It could be more focused on the tool itself, but the necessary information for calling the tool is present.

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 description coverage is 100% and the action enum and params object are fully documented in the schema. The description adds no parameter-specific semantics beyond what the schema already provides, so baseline 3 is appropriate.

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 the resource (Bing Webmaster Tools organic-search data) and enumerates the data domains it returns. It is specific but does not explicitly contrast with sibling connectors like search_console_connector or ahrefs_connector.

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?

Lists clear use cases (Bing SEO reporting, organic-search visibility, keyword analysis, crawl health, backlink volume). However, it offers no exclusions or guidance on when to choose this connector over alternatives like bing_webmaster_dashboard or search_console_connector.

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

All CorpusIQ tools Inspect

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

Need Help?