Skip to main content
Glama
occirank

Haloscan MCP Server

by occirank

get_domains_gmb_backlinks_map

Retrieves a map of backlinks for Google My Business domains, enabling SEO analysis of local business link profiles.

Instructions

Obtenir la carte des backlinks des domaines GMB.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYes
modeNo
Behavior2/5

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

No annotations provided, so description must disclose behavior. It only says 'carte des backlinks' without specifying output format (e.g., URL, data map) or safety profile (read vs. destructive). Lack of detail leaves agent guessing.

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?

One short sentence, efficient in length but lacks critical details. Some waste by not explaining parameters; conciseness is acceptable but not optimal given missing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no annotations, and two undocumented parameters, the description is insufficient. Agent cannot determine expected output, parameter usage, or when to invoke this tool.

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 coverage is 0% with no parameter descriptions. The description adds no meaning for 'input' or 'mode'. Agent has no clue what these parameters represent or how to format them.

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

Purpose4/5

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

The description clearly states the verb and resource: 'Obtenir la carte des backlinks des domaines GMB.' It directly indicates the tool's purpose and distinguishes it from siblings like get_domains_gmb_backlinks (likely list) and get_domains_gmb_backlinks_categories, though it does not explicitly differentiate.

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 alternatives such as get_domains_gmb_backlinks or get_domains_gmb_backlinks_categories. No context about prerequisites or typical scenarios.

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