Skip to main content
Glama
occirank

Haloscan MCP Server

by occirank

get_keywords_find

Find relevant keywords using filters like search volume, CPC, competition, and KGR. Specify seed keywords and optional exact match.

Instructions

Trouver 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
keywordNoSeed keyword
keywordsNo
keywords_sourcesNo
keep_seedNo
exact_matchNo
Behavior1/5

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

No annotations are provided, and the description does not disclose any behavioral traits (e.g., read-only, destructive, rate limits) beyond the verb 'find', which is already obvious from the name.

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

Conciseness1/5

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

While short, the description is severely underspecified, not concise. It lacks any front-loaded essential information and contains no meaningful content.

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?

With 25 parameters, no output schema, and no annotations, the description is completely inadequate. It fails to explain what the tool returns, how to use filters, or any operational context.

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 16%, and the tool description adds no parameter explanations whatsoever. The 84% of undocumented parameters lack any context from the description.

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

Purpose1/5

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

The description 'Trouver des mots-clés' is a tautology of the tool name (get_keywords_find), restating it in French. It fails to specify what kind of keyword finding operation this performs, especially given numerous sibling tools like get_keywords_related, get_keywords_similar, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage guidance provided; there is no mention of when to use this tool versus alternatives, no prerequisites, and no 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