Skip to main content
Glama
Teake1404

seo-data-api-mcp-server

by Teake1404

Keyword Questions

keywordsQuestions

Retrieve questions people ask about a seed keyword from a regional database. Filter by search volume, difficulty, CPC, and competition to identify content opportunities.

Instructions

Fetch keyword questions (v1/keywords/questions)

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.
Behavior1/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only mentions the API endpoint and fails to state any behavioral traits like read-only nature, pagination behavior, response format, or side effects. This is a critical gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (one phrase) which is concise but lacks structure or complete sentences. It is not front-loaded with key information; it barely communicates purpose. A 3 is adequate but not well-crafted.

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 the tool has 20 parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the tool returns, how to interpret results, or any usage constraints. A 1 indicates significant gaps.

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 all parameters have descriptions in the schema. The tool description itself adds no additional meaning beyond the schema. Baseline 3 is appropriate as the description does not detract but adds no value.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Fetch keyword questions' which is a specific verb and resource, but it lacks any explanation of what 'keyword questions' are, making it minimally clear. It does not distinguish from sibling tools like keywordsSimilar or keywordsLongtail. A score of 3 reflects adequate but not differentiating clarity.

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?

The description provides no guidance on when to use this tool versus alternatives, such as when a user needs question-based keywords versus related keywords or long-tail keywords. There are no explicit usage contexts or exclusions.

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