Skip to main content
Glama
occirank

Haloscan MCP Server

by occirank

get_keywords_highlights

Extract keyword highlights such as search volume, CPC, competition, and KGR for a seed keyword, with sorting and filtering options.

Instructions

Obtenir les points forts des mots-clés.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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
word_count_minNo
word_count_maxNo
includeNo
excludeNo
keywordYesSeed keyword
exact_matchNo
similarity_minNo
similarity_maxNo
Behavior1/5

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

No annotations are provided, and the description fails to disclose behavioral traits such as read/write nature, rate limits, or any side effects.

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 short sentence, which is concise but lacks essential detail and structure to be helpful.

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 24 parameters, no output schema, and no annotations, the description is severely incomplete; it does not explain return values, filtering, or behavior.

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 only 17% schema description coverage, the description adds no meaning to the 24 parameters; many parameters remain undocumented and the description does not clarify them.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get the highlights of keywords' is vague; it does not specify what constitutes 'highlights' or distinguish it from siblings like get_keywords_overview or get_keywords_bulk.

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 context or exclusions.

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