Skip to main content
Glama
zhangluka

grain-seo-mcp

by zhangluka

bing_brand_analysis

Compare brand and non-brand keyword performance on Bing to identify traffic sources and optimize SEO strategy.

Instructions

Analyze Brand vs Non-Brand performance on Bing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
siteUrlYesThe URL of the site
brandRegexYesRegex matching brand terms (e.g. 'acme|acmecorp')
daysNoNumber of days to analyze (default 28)
Behavior2/5

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

No annotations are provided, so the description must convey behavioral traits. It only states 'Analyze... performance' without indicating whether it is read-only, requires authentication, or affects data. The agent cannot infer safety or side effects.

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?

The description is a single concise sentence that front-loads the purpose. However, it could be improved by adding brief usage context without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and only three parameters, the description is too sparse. It omits return format, interpretation of results, and any behavioral details, making it incomplete for an AI agent to fully understand the tool's capabilities.

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 description does not add extra meaning beyond the schema's parameter descriptions. Baseline 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?

The description clearly states the tool's verb ('Analyze'), resource ('Brand vs Non-Brand performance'), and platform ('Bing'), distinguishing it from siblings like 'seo_brand_vs_nonbrand' for Google.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives, nor any context about prerequisites or scenarios where it is not appropriate.

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/zhangluka/grain-seo-mcp'

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