Skip to main content
Glama
Teake1404

seo-data-api-mcp-server

by Teake1404

Domain Keywords Reverse Comparison

domainKeywordsReverseComparison

Compare keywords between two domains to identify overlapping and unique rankings. Specify organic or paid search for analysis.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sourceYesAlpha-2 country code of the regional keyword database.
domainYesThe primary domain for the comparison.
compareYesThe competitor domain to compare against the primary domain.
typeNoSpecifies whether to compare keywords based on organic search traffic or paid search (advertising) traffic.organic
pageNoFor paginated results, specifies the page number of keywords to retrieve.
limitNoThe maximum number of keywords to return per page.
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.
order_fieldNoSpecifies the field by which to sort the results.keyword
order_typeNoSpecifies the sort order for the results.asc
Behavior1/5

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

No annotations provided, so the description must disclose behavioral traits. It fails to mention any: no indication of side effects (likely read-only but unstated), no rate limits, no auth requirements. The bare description adds nothing.

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?

The description is a single sentence but is under-specified, providing minimal value. It does not effectively front-load key information.

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 9 parameters, no output schema, and no annotations, the description is far from complete. It lacks explanation of result format, pagination details, or how the comparison differs from similar tools.

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

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 'Compare keywords across domains' which indicates the core action and resource, but it lacks differentiation from the sibling tool 'domainKeywordsComparison'. The term 'Reverse' in the title is not explained.

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 on when to use this tool versus the similar sibling 'domainKeywordsComparison'. No context about prerequisites or typical use cases.

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