Skip to main content
Glama
Teake1404

seo-data-api-mcp-server

by Teake1404

Domain Keywords

domainKeywords

Fetch organic or paid keywords for a domain, filtered by country, search volume, difficulty, position, and ranking changes.

Instructions

Fetch domain keywords (v1/domain/keywords)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesAlpha-2 country code of the regional keyword database.
domainYesThe domain name for which to retrieve keywords.
typeNoSpecifies whether to retrieve keywords for organic search traffic or paid search (advertising) traffic.organic
order_fieldNoThe field by which the returned keyword list should be sorted.traffic
order_typeNoThe order of sorting.desc
pageNoFor paginated results, specifies the page number to retrieve.
limitNoThe maximum number of keywords to return per page.
colsNoA comma-separated list of specific response parameter names to include in the output. If omitted, a default set of relevant columns is returned.
pos_changeNoFilters keywords based on changes in their ranking positions compared to the previous period.
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.
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only gives the endpoint path, omitting details like read-only nature, required authentication, rate limits, or error scenarios. This is insufficient for safe invocation.

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 a single sentence that essentially repeats the endpoint name. It is under-specified and fails to provide useful information efficiently.

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

Completeness1/5

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

Given 26 parameters, no output schema, and no annotations, the description is extremely incomplete. It lacks information on pagination, sorting, filtering semantics, return format, and behavior with invalid inputs.

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 schema already documents all 26 parameters. The description adds no extra meaning beyond the schema, meeting the baseline of 3.

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 clearly states the verb 'Fetch' and the resource 'domain keywords', making the tool's core purpose unambiguous. However, it does not distinguish this tool from siblings like 'domainKeywordsComparison' or 'keywordsLongtail', missing a chance to differentiate.

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 is provided on when to use this tool versus alternatives. Among many sibling keyword tools, explicit when-to-use and when-not-to-use advice would significantly help an agent select correctly.

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