Skip to main content
Glama
occirank

Haloscan MCP Server

by occirank

get_domains_competitors_keywords_best_pos

Retrieve top keyword positions for competitor domains. Analyzes competitor keywords to identify best ranking positions.

Instructions

Obtenir les meilleures positions des mots-clés des concurrents des domaines.

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
competitorsYes
keywordsYes
best_competitor_traffic_minNo
best_competitor_traffic_maxNo
best_competitor_traffic_keep_naNo
best_competitor_position_minNo
best_competitor_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
Behavior2/5

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

No annotations exist, and the description does not disclose behavioral traits such as whether the tool is read-only, destructive, rate-limited, or requires authorization. For a complex tool with 37 parameters, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence, but it lacks structure and is under-specified for the tool's complexity. While not verbose, it does not earn its place by providing necessary detail.

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 tool's 37 parameters, low schema coverage, no output schema, and missing annotations, the description is woefully incomplete. An AI agent cannot effectively determine inputs, outputs, or behavior from this description alone.

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?

With schema description coverage at only 8%, the description does not compensate. It fails to explain the meaning or relationship of the 37 parameters, many of which have no descriptions in the schema, leaving the AI agent guessing.

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 retrieves 'best positions' of competitors' keywords, providing a specific verb and resource. However, it is vague about what 'best positions' means and does not differentiate from sibling tools like 'get_domains_competitors_keywords_diff' or 'get_domains_competitors_best_pages'.

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 lacks any context about prerequisites, use cases, or exclusions given the numerous sibling tools.

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