Skip to main content
Glama
Teake1404

seo-data-api-mcp-server

by Teake1404
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Longtail Keywords

keywordsLongtail

Fetch longtail keywords with low search volume from a specified country database. Filter by metrics like volume, difficulty, CPC, and competition to find niche keyword opportunities.

Instructions

Fetch longtail (low search volume) keywords (v1/keywords/longtail)

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.
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.

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?

No annotations are provided, so the description carries the full burden. It only says 'Fetch', implying a read operation, but does not disclose response format, pagination behavior, rate limits, or any other behavioral traits.

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 a single compact sentence with the key concept front-loaded. The endpoint string 'v1/keywords/longtail' is somewhat redundant but does not add meaningful clutter.

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 19 parameters, no annotations, and no output schema, a one-line description is insufficient. It does not explain what the result contains, how longtail differs operationally from similar tools, or what the agent should expect after invocation.

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 schema already documents all 19 parameters. The description adds no parameter-level meaning beyond the longtail/low-volume concept.

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 clear action and resource: 'Fetch longtail ... keywords' and clarifies the meaning with '(low search volume)'. It is distinct enough from siblings like keywordsSimilar or keywordsRelated, though it never explicitly differentiates from them.

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 gives no guidance on when to use this tool instead of alternatives such as keywordsSimilar or keywordsRelated. No use cases, exclusions, or selection criteria are provided.

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