Skip to main content
Glama
patchwindow

seo-mcp

by patchwindow

bing_keyword_research

Get monthly search volume and related keywords from Bing Webmaster Tools to discover exclusive Bing keyword data not available in Google Search Console.

Instructions

Research keywords using Bing Webmaster Tools. Returns monthly search volume (impressions) for a keyword and a list of related keywords. This keyword data is exclusive to Bing and not available in Google Search Console.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYesThe keyword to research.
site_urlNoYour site URL in Bing Webmaster Tools, e.g. 'https://example.com/'. Uses config default if omitted.
countryNoTwo-letter country code (e.g. 'US', 'GB'). Default: 'US'.
languageNoLanguage code (e.g. 'en-US'). Default: 'en-US'.
include_relatedNoInclude related keywords. Default: true.
Behavior3/5

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

No annotations provided, so description must cover behavioral traits. It states what is returned (volume, related keywords) but omits details like read-only nature, rate limits, or authorization needs.

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

Conciseness5/5

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

Two focused sentences; no wasted words. Purpose and key differentiating fact are front-loaded.

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 5 parameters, no output schema, and no annotations, description covers the main purpose and data source. Could mention return format, but tool is simple enough that context is mostly complete.

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 100%, so schema already documents parameters. Description adds no extra meaning beyond schema, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool researches keywords using Bing Webmaster Tools, returns search volume and related keywords, and distinguishes itself from siblings by noting Bing's exclusivity.

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

Usage Guidelines3/5

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

Implies usage for Bing keyword data, but lacks explicit guidance on when to use vs alternatives, no when-not or alternative mentions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/patchwindow/seo-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server