Skip to main content
Glama
TeamDay-AI

SE Ranking MCP Server

by TeamDay-AI

Related Keywords

DATA_getRelatedKeywords

Retrieves semantically related keywords for a seed keyword using a regional database. Filter results by search volume, CPC, difficulty, competition, and more to refine keyword research.

Instructions

Data Tool: Retrieves a list of keywords semantically related to the seed keyword.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoThe field by which the returned list of keywords should be sorted.
limitNoMaximum number of keywords to return per page.
offsetNoStarting offset for pagination.
sourceYesAlpha-2 country code of the regional keyword database.
keywordYesThe seed keyword for which to find similar keywords.
sort_orderNoThe order of sorting for the sort field.desc
filter_cpc_toNoMaximum Cost Per Click.
history_trendNoWhether to include historical search volume trend data in the response.
filter_intentsNoComma-separated list of search intent codes: I=Informational, N=Navigational, T=Transactional, C=Commercial, L=Local.
filter_cpc_fromNoMinimum Cost Per Click.
filter_volume_toNoMaximum monthly search volume.
filter_volume_fromNoMinimum monthly search volume.
filter_difficulty_toNoMaximum keyword difficulty score (0-100).
filter_serp_featuresNoComma-separated list of SERP features to filter by.
filter_competition_toNoMaximum competition score (0.0-1.0).
filter_difficulty_fromNoMinimum keyword difficulty score (0-100).
filter_competition_fromNoMinimum competition score (0.0-1.0).
filter_keyword_count_toNoMaximum number of words in the keyword.
filter_keyword_count_fromNoMinimum number of words in the keyword.
filter_characters_count_toNoMaximum character length of the keyword.
filter_characters_count_fromNoMinimum character length of the keyword.
filter_multi_keyword_excludedNoComma-separated list of words that must NOT appear in the keyword.
filter_multi_keyword_includedNoComma-separated list of words that MUST appear in the keyword (AND logic).
Behavior2/5

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

No annotations are provided, and the description does not disclose behavioral traits like pagination, sorting, or the extensive filtering capabilities implied by the schema. The agent is left uninformed about these important aspects.

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?

Very concise single sentence, but it could include more useful information without becoming overly long. The front-loaded structure is good.

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?

With 23 parameters and no output schema, the description is far too sparse. It fails to mention the rich filtering, sorting, and pagination options, leaving the agent with an incomplete picture of the tool's capabilities.

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 baseline is 3. The description adds no additional meaning beyond what the parameter descriptions already provide.

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 it retrieves semantically related keywords for a seed keyword. While it doesn't explicitly differentiate from sibling tools like DATA_getSimilarKeywords, the mention of 'semantically related' provides enough specificity.

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 versus alternatives such as DATA_getSimilarKeywords or DATA_getDomainKeywords. The description lacks context on typical use cases or prerequisites.

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