Skip to main content
Glama
zhangluka

grain-seo-mcp

by zhangluka

brand_analysis

Compare brand and non-brand search performance by integrating data from Google Search Console, Bing Webmaster Tools, and GA4 to identify traffic sources and optimization opportunities.

Instructions

Analyze Brand vs Non-Brand performance across GSC, Bing, and GA4

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
brandTermsYesList of brand keywords
gscSiteUrlYesGSC Site URL
bingSiteUrlYesBing Site URL
ga4PropertyIdYesGA4 Property ID
startDateYesStart date (YYYY-MM-DD)
endDateYesEnd date (YYYY-MM-DD)
ga4AccountIdNoOptional GA4 account ID
gscAccountIdNoOptional GSC account ID
bingAccountIdNoOptional Bing account ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided, so the description must carry the burden. It does not disclose whether the tool performs read-only analysis, what data is aggregated, any permissions required, or implications of the analysis (e.g., rate limits across sources).

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?

Single sentence, front-loaded with key information. No wasted words, but could be slightly expanded to improve other dimensions 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?

Tool has 9 parameters, 3 data sources, no output schema, and fairly complex analysis. Description lacks details on expected output, prerequisites (e.g., account linking), and how results are presented.

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 baseline is 3. Description adds slight context by listing the three sources, but does not explain how parameters like brandTerms interact or required formats for dates or URLs.

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 verb 'Analyze', the resource 'Brand vs Non-Brand performance', and the data sources 'GSC, Bing, and GA4'. This distinguishes it from sibling tools like seo_brand_vs_nonbrand which may focus on a single source.

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?

No guidance on when to use this tool vs alternatives such as seo_brand_vs_nonbrand or bing_brand_analysis. The description does not provide context for selection or prerequisites.

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

Deploy Server

Other Tools