Skip to main content
Glama
Sign In
seo-mcp

seo-mcp

by patchwindow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

gsc_brand_nonbrand

Segment Google Search Console traffic by branded vs. non-branded queries. Get aggregated clicks, impressions, CTR, position, and top queries for each segment.

Instructions

Split search traffic into branded and non-branded query segments. Returns aggregated clicks, impressions, CTR, and position for each segment, plus top queries.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start_date": "<start_date>",
      "end_date": "<end_date>",
      "brand_terms": "<brand_terms>"
    },
    "name": "gsc_brand_nonbrand"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_urlNoSite URL in GSC format, e.g. 'sc-domain:example.com'. Uses config default if omitted.
start_dateYesStart date in YYYY-MM-DD format.
end_dateYesEnd date in YYYY-MM-DD format.
brand_termsYesBrand terms to match against queries (case-insensitive). Any query containing one of these is classified as branded. Example: ['acme', 'acmecorp'].
show_top_queriesNoInclude top 10 branded and non-branded queries. Default: true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.7/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. It discloses that the split is based on brand_terms and returns aggregated metrics and top queries, but lacks details on data source (GSC API), rate limits, data freshness, or error cases.

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 sentences, no wasted words, front-loaded with the tool's core purpose. Every sentence adds essential information.

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

Completeness3/5

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

Given no output schema, the description partially explains return values but lacks format details (e.g., structure of top queries) and omits prerequisites like GSC access. Adequate but not fully comprehensive for a tool with 5 parameters and no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with descriptions for all 5 parameters. The description adds value by explaining the output (aggregated clicks, impressions, CTR, position per segment, plus top queries), which goes beyond the schema's parameter-level docs.

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 uses a specific verb ('split') and resource ('search traffic into branded and non-branded query segments') and clearly distinguishes from siblings like gsc_search_performance, which provides overall performance, and gsc_striking_distance, which focuses on near-top pages.

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?

The description implies usage for brand vs non-brand analysis but does not explicitly state when to use this tool over alternatives or provide exclusion criteria. No guidance on prerequisites or context.

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