Skip to main content
Glama
Teake1404

seo-data-api-mcp-server

by Teake1404

Related Keywords

keywordsRelated

Find related keywords for a seed keyword, with filters for search volume, difficulty, CPC, and competition, to expand your SEO keyword list.

Instructions

Fetch related keywords (v1/keywords/related)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesAlpha-2 country code of the regional keyword database.
keywordYesThe seed keyword for which to find similar keywords.
limitNoMaximum number of keywords to return per page.
offsetNoStarting offset for pagination.
sortNoThe field by which the returned list of keywords should be sorted.
sort_orderNoThe order of sorting for the sort field.desc
history_trendNoWhether to include historical search volume trend data in the response.
filter[volume][from]NoMinimum monthly search volume.
filter[volume][to]NoMaximum monthly search volume.
filter[difficulty][from]NoMinimum keyword difficulty score (0-100).
filter[difficulty][to]NoMaximum keyword difficulty score (0-100).
filter[cpc][from]NoMinimum Cost Per Click.
filter[cpc][to]NoMaximum Cost Per Click.
filter[competition][from]NoMinimum competition score (0.0-1.0).
filter[competition][to]NoMaximum competition score (0.0-1.0).
filter[keyword_count][from]NoMinimum number of words in the keyword.
filter[keyword_count][to]NoMaximum number of words in the keyword.
filter[characters_count][from]NoMinimum character length of the keyword.
filter[characters_count][to]NoMaximum character length of the keyword.
filter[serp_features]NoComma-separated list of SERP features to filter by.
Behavior2/5

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

With no annotations, the description carries full burden but only mentions the API endpoint. It fails to disclose pagination, rate limits, data freshness, or what 'related' means behaviorally.

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?

While brief, the description is undersized for the complexity (20 params). It lacks front-loaded details and reads as a tautology of the name.

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?

The description is completely inadequate for a tool with 20 parameters, no output schema, and no annotations. It does not explain return structure, pagination, or the meaning of 'related'.

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 baseline is 3. The description adds no parameter-level meaning beyond what the schema already provides.

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 related keywords' clearly states the action and resource. However, it does not differentiate from sibling tools like keywordsSimilar or keywordsLongtail, which may overlap in concept.

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 vs alternatives. The description simply states what it does without context for selection among siblings.

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