Skip to main content
Glama
guifreballester-seranking

SE Ranking SEO Data API MCP Server

by guifreballester-seranking
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Domain Keywords Reverse Comparison

domainKeywordsReverseComparison

Compare organic or paid keywords between two domains to uncover shared keywords, gaps, and competitive positioning in search results.

Instructions

Compare keywords across domains (v1/domain/keywords/comparison)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colsNoA comma-separated list of specific response parameter names to include in the output. If omitted, a default set of relevant columns is returned for the comparison.
pageNoFor paginated results, specifies the page number of keywords to retrieve.
typeNoSpecifies whether to compare keywords based on organic search traffic or paid search (advertising) traffic.organic
limitNoThe maximum number of keywords to return per page.
domainYesThe primary domain for the comparison.
sourceYesAlpha-2 country code of the regional keyword database.
compareYesThe competitor domain to compare against the primary domain.
order_typeNoSpecifies the sort order for the results.asc
order_fieldNoSpecifies the field by which to sort the results.keyword

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.6/5.0
Behavior1/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 of behavioral disclosure. It does not mention whether this is a read-only operation, what output format to expect, how pagination or sorting behave, or what 'reverse' means. The description only restates the operation without disclosing behavior.

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 concise sentence with no redundant content. It is brief, but this brevity comes at the cost of missing important context.

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?

This tool has 9 parameters, no output schema, no annotations, and a closely related sibling tool (domainKeywordsComparison). The description provides only a minimal phrase and fails to explain the reverse comparison semantics, result behavior, or when to choose this tool, leaving agents under-equipped.

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?

The input schema already documents all parameters with 100% coverage, so the baseline is 3. The description adds no parameter meaning beyond the schema, but it does not need to because the schema is self-sufficient.

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: 'Compare keywords across domains.' However, it does not explain what 'Reverse' adds relative to the sibling tool domainKeywordsComparison, so it does not fully distinguish itself.

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?

There is no guidance about when to use this tool versus domainKeywordsComparison or any other sibling. The description only implies a general use case and provides no exclusions or alternative routing.

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