Skip to main content
Glama
Teake1404

seo-data-api-mcp-server

by Teake1404

AIO Keywords by Brand

domainAioKeywordsByBrand

Retrieve AI Overview keywords by brand for a specified domain (base, host, or URL) with filters for volume, difficulty, intent, and other SEO metrics.

Instructions

Fetch AI Overviews domain keywords by brand (v1/domain/aio/keywords-by-brand)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesThe alpha-2 country code for the regional database. Example: us
brandYesThe brand name to search for in AIO snippets. Example: SE Ranking.
scopeNoThe scope of the analysis. Can be base_domain (domain and all subdomains), domain (specific host), or url (exact URL).base_domain
sortNoThe field to sort the results by. Available values: volume, type, snippet_length.volume
sort_orderNoThe order for sorting. Available values: asc, desc.desc
offsetNoThe starting position for paginated results.
limitNoThe maximum number of keywords to return per page.
filter[volume][from]NoSpecifies the minimum monthly search volume for keywords to be included.
filter[volume][to]NoSpecifies the maximum monthly search volume for keywords to be included.
filter[difficulty][from]NoSpecifies the minimum keyword difficulty score (typically 0-100) for keywords to be included.
filter[difficulty][to]NoSpecifies the maximum keyword difficulty score for keywords to be included.
filter[keyword_count][from]NoSpecifies the minimum number of words in a keyword phrase.
filter[keyword_count][to]NoSpecifies the maximum number of words in a keyword phrase.
filter[intents]NoA comma-separated list of search intent codes to filter keywords.
filter[competition][from]NoSpecifies the minimum competition score (typically 0-1 or 0-100, depending on the metric scale) for keywords.
filter[competition][to]NoSpecifies the maximum competition score for keywords.
filter[cpc][from]NoSpecifies the minimum Cost Per Click (CPC) value for keywords.
filter[cpc][to]NoSpecifies the maximum Cost Per Click (CPC) value for keywords.
filter[traffic][from]NoSpecifies the minimum estimated monthly traffic for keywords.
filter[traffic][to]NoSpecifies the maximum estimated monthly traffic for keywords.
filter[position][from]NoSpecifies the minimum ranking position for keywords.
filter[position][to]NoSpecifies the maximum ranking position for keywords.
filter[characters_count][from]NoSpecifies the minimum character length for keyword phrases.
filter[characters_count][to]NoSpecifies the maximum character length for keyword phrases.
Behavior1/5

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

No annotations are provided, so the description must disclose behavioral traits. It only provides the endpoint path, omitting any details about authentication, rate limits, data freshness, pagination limits, or what happens with missing brands. This is severely lacking.

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 extremely short (one sentence) but under-specified. It provides no helpful structure or front-loaded key information. It sacrifices completeness for brevity, making it less useful.

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?

The tool has 24 parameters, 2 required, and no output schema. The description is far too minimal to cover the complexity. It does not explain return structure, pagination, or how filters interact, leaving the agent with only the schema to infer behavior.

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%, so the input schema already documents each parameter's meaning. The description adds no additional semantic value beyond the endpoint context. 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?

The description 'Fetch AI Overviews domain keywords by brand' clearly states the verb (fetch) and resource (AIO domain keywords by brand). It distinguishes from sibling tools like domainAioKeywordsByTarget, but does not explicitly mention how it differs, so it's not a full 5.

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 like domainAioKeywordsByTarget or domainAioOverview. The description fails to provide context for selection, leaving the agent to infer from the name alone.

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/Teake1404/seo-data-api-mcp-server'

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