Skip to main content
Glama
TeamDay-AI

SE Ranking MCP Server

by TeamDay-AI

Domain Keywords

DATA_getDomainKeywords

Retrieve keywords ranking for a domain in organic or paid search, with filters for position, volume, CPC, intent, and more.

Instructions

Data Tool: Retrieves a list of keywords for which a domain ranks in organic or paid search.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoExact URL for which to retrieve keyword rankings.
colsNoA comma-separated list of specific response parameter names to include in the output. If omitted, a default set of relevant columns is returned.
pageNoFor paginated results, specifies the page number to retrieve.
typeNoSpecifies whether to retrieve keywords for organic search traffic or paid search (advertising) traffic.organic
limitNoThe maximum number of keywords to return per page.
domainYesThe domain name for which to retrieve keywords.
sourceYesAlpha-2 country code of the regional keyword database.
filter_urlNoJSON string to filter keywords by ranking URL.
order_typeNoThe order of sorting.desc
pos_changeNoFilters keywords based on changes in their ranking positions compared to the previous period.
order_fieldNoThe field by which the returned keyword list should be sorted.traffic
filter_cpc_toNoSpecifies the maximum Cost Per Click (CPC) value for keywords.
filter_intentsNoA comma-separated list of search intent codes to filter keywords.
filter_keywordNoJSON string specifying keyword text to match.
filter_cpc_fromNoSpecifies the minimum Cost Per Click (CPC) value for keywords.
filter_price_toNoMaximum keyword price value.
with_subdomainsNoIf set to true, includes keywords ranking for the specified domain or URL and all its subdomains.
filter_volume_toNoSpecifies the maximum monthly search volume for keywords to be included.
filter_price_fromNoMinimum keyword price value.
filter_traffic_toNoSpecifies the maximum estimated monthly traffic for keywords.
filter_position_toNoSpecifies the maximum ranking position for keywords.
filter_volume_fromNoSpecifies the minimum monthly search volume for keywords to be included.
filter_traffic_fromNoSpecifies the minimum estimated monthly traffic for keywords.
filter_difficulty_toNoSpecifies the maximum keyword difficulty score for keywords to be included.
filter_position_fromNoSpecifies the minimum ranking position for keywords.
filter_serp_featuresNoComma-separated list of SERP feature codes to include (e.g., featured_snippet,local_pack,sitelinks).
filter_competition_toNoSpecifies the maximum competition score for keywords.
filter_difficulty_fromNoSpecifies the minimum keyword difficulty score (typically 0-100) for keywords to be included.
filter_competition_fromNoSpecifies the minimum competition score (typically 0-1 or 0-100, depending on the metric scale) for keywords.
filter_keyword_count_toNoSpecifies the maximum number of words in a keyword phrase.
filter_keyword_count_fromNoSpecifies the minimum number of words in a keyword phrase.
filter_traffic_percent_toNoMaximum traffic share percentage for keywords.
filter_characters_count_toNoSpecifies the maximum character length for keyword phrases.
filter_traffic_percent_fromNoMinimum traffic share percentage for keywords.
filter_characters_count_fromNoSpecifies the minimum character length for keyword phrases.
filter_multi_keyword_excludedNoJSON string specifying keyword text that must be excluded.
filter_multi_keyword_includedNoJSON string specifying keyword text that must be included.
Behavior2/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 states it retrieves data, without mentioning if it is read-only, pagination behavior, or any side effects. The description is insufficient for a data tool.

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?

The description is a single concise sentence that front-loads the core purpose. No unnecessary words.

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?

Despite 37 parameters and no output schema, the description does not mention return format, pagination, or key usage notes. Users would need to infer behavior from the schema alone.

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 the baseline is 3. The description adds no additional meaning beyond the schema; all parameter details are in the input schema itself.

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 retrieves keywords for a domain, specifying both organic and paid search. It uses a specific verb and resource, distinguishing it from sibling tools like DATA_getDomainKeywordsComparison.

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 retrieving domain keywords but does not provide explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives among sibling tools.

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/TeamDay-AI/se-ranking-mcp'

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