Skip to main content
Glama
occirank

Haloscan MCP Server

by occirank

get_domains_competitors_keywords_diff

Identify keyword gaps between your domain and competitors by comparing keyword sets and applying filters like volume, CPC, and competition.

Instructions

Obtenir la différence de mots-clés entre les domaines et leurs concurrents.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNo
lineCountNoMax number of returned results.
order_byNoField used for sorting results. Default sorts by descending volume.
orderNoWhether the results are sorted in ascending or descending order.
volume_minNo
volume_maxNo
cpc_minNo
cpc_maxNo
competition_minNo
competition_maxNo
kgr_minNo
kgr_maxNo
kvi_minNo
kvi_maxNo
kvi_keep_naNo
allintitle_minNo
allintitle_maxNo
inputYes
competitorsNo
exclusiveNo
missingNo
bestingNo
bestedNo
acceptedTypesNo
pageNo
best_competitor_traffic_minNo
best_competitor_traffic_maxNo
best_competitor_traffic_keep_naNo
best_reference_traffic_minNo
best_reference_traffic_maxNo
best_reference_traffic_keep_naNo
best_reference_position_minNo
best_reference_position_maxNo
competitors_positions_minNo
competitors_positions_maxNo
unique_competitors_count_minNo
unique_competitors_count_maxNo
keyword_word_count_minNo
keyword_word_count_maxNo
keyword_includeNo
keyword_excludeNo
volume_keep_naNo
cpc_keep_naNo
competition_keep_naNo
kgr_keep_naNo
allintitle_keep_naNo
google_indexed_minNo
google_indexed_maxNo
google_indexed_keep_naNo
Behavior1/5

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

With no annotations, the description must disclose behavioral traits. It only says 'get difference' with no mention of side effects, rate limits, authentication, or what the output represents. This is a critical gap for a tool with 49 parameters.

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 concise but under-specified. It is a single sentence that adds no value beyond the name, missing necessary details to be effectively used.

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 high parameter count, lack of annotations, and absent output schema, the description is severely incomplete. It fails to provide enough context for an agent to understand the tool's function or how to use it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 6%, and the tool description adds no information about parameters. The description does not explain the many filter and sorting parameters, leaving the agent blind to their meaning.

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 the tool gets keyword differences between domains and competitors, which matches the name. However, it does not distinguish it from sibling tools like get_domains_competitors or get_domains_competitors_keywords_best_pos, and the description is essentially a translation of the name without additional specificity.

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 provided on when to use this tool versus alternatives. The description does not mention prerequisites, context, or exclusions, leaving the agent without direction for proper invocation.

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/occirank/Haloscan-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server