Skip to main content
Glama
occirank

Haloscan MCP Server

by occirank

get_domains_gmb_backlinks

Obtain backlinks from Google My Business domains. Use filters like rating, location, and categories to target specific businesses.

Instructions

Obtenir les backlinks des domaines GMB.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputNoRequested URL or domain
modeNoWhether to look for a domain or a full url. Leave empty for auto detection (options: auto, root, domain, url)
lineCountNoMax number of returned results (default: 20)
pageNoPage number (default: 1)
order_byNoField used for sorting results. Options: default, rating_count, rating_value, is_claimed, total_photos, name, address, phone, longitude, latitude, categories, url, domain, root_domain
orderNoWhether results are sorted in ascending or descending order (asc, desc)
rating_count_minNo
rating_count_maxNo
rating_count_keep_naNo
rating_value_minNo
rating_value_maxNo
rating_value_keep_naNo
latitude_minNo
latitude_maxNo
latitude_keep_naNo
longitude_minNo
longitude_maxNo
longitude_keep_naNo
categories_includeNoRegular expression for keywords to be included
categories_excludeNoRegular expression for keywords to be excluded
is_claimedNoWhen FALSE, only return unclaimed companies. When TRUE, only return claimed companies. Leave empty if you don't want to filter.
Behavior2/5

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

No annotations are provided, and the description is only one sentence. It does not disclose any behavioral traits such as input validation, rate limits, or the nature of the output. The description carries the full burden but fails to deliver.

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?

Extremely concise (one sentence), but it is under-specified rather than concise. Lacks front-loaded essential information; the single sentence does not earn its place as it provides minimal value.

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 21 parameters, no output schema, and many sibling tools, the description is severely incomplete. It fails to explain input format, filtering capabilities, or even the basic meaning of GMB. The agent cannot effectively invoke the tool.

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

Parameters2/5

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

Schema coverage is 43% (only 9 of 21 parameters have descriptions). The description adds no information about parameters, leaving many fields like rating_count_min, latitude_min, and filtering options unexplained. The description should compensate but does not.

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 backlinks of GMB domains, which is clear but does not differentiate from sibling tools like get_domains_gmb_backlinks_categories or get_domains_gmb_backlinks_map. The acronym GMB is not explained, assuming domain knowledge.

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, no prerequisites, no conditions for use. The agent has no context to choose this tool over others.

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