Skip to main content
Glama
guifreballester-seranking

SE Ranking SEO Data API MCP Server

by guifreballester-seranking
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Keyword Questions

keywordsQuestions

Retrieve question-based keywords related to a seed keyword to uncover user queries, supporting FAQ schema and content targeting.

Instructions

Fetch keyword questions (v1/keywords/questions)

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
history_trendNoWhether to include historical search volume trend data in the response.
filter[cpc][to]NoMaximum Cost Per Click.
filter[cpc][from]NoMinimum Cost Per Click.
filter[volume][to]NoMaximum monthly search volume.
filter[volume][from]NoMinimum monthly search volume.
filter[serp_features]NoComma-separated list of SERP features to filter by.
filter[difficulty][to]NoMaximum keyword difficulty score (0-100).
filter[competition][to]NoMaximum competition score (0.0-1.0).
filter[difficulty][from]NoMinimum keyword difficulty score (0-100).
filter[competition][from]NoMinimum competition score (0.0-1.0).
filter[keyword_count][to]NoMaximum number of words in the keyword.
filter[keyword_count][from]NoMinimum number of words in the keyword.
filter[characters_count][to]NoMaximum character length of the keyword.
filter[characters_count][from]NoMinimum character length of the keyword.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only indicates a read operation. It does not mention response format, pagination behavior, meaning of keyword questions, or any caveats such as required auth or API limits.

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?

The description is one efficient, front-loaded sentence with no filler. It conveys the action and endpoint compactly, though it sacrifices useful context for brevity.

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?

For a tool with 20 parameters, no output schema, and no annotations, this single sentence is not enough context. The agent is left to infer what a keyword question is, what the response contains, and how limit/offset pagination behaves.

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?

All parameters are already documented in the input schema, so the description does not need to repeat them. The schema covers defaults, enums, and filters, meeting the baseline for parameter semantics.

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 states a specific verb and resource: 'Fetch keyword questions', and exposes the exact endpoint v1/keywords/questions. It is not a tautology and clearly names the operation, though it does not explain how it differs from sibling keyword tools.

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 given about when to prefer this tool over alternatives such as keywordsSimilar, keywordsRelated, or keywordsLongtail. The intended use case is only implied by the name and the single verb 'Fetch'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools