get_unique_domain_backlinks
Get unique domain backlinks
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| num | No | Number of results to return (max 1000) | |
| domain | Yes | Domain to analyze (e.g., example.com) |
xpay✦ Marketing Collection
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
C2.8/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden for behavioral disclosure. It only states the basic function, omitting details about return format, deduplication logic, rate limits, or authentication requirements.
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 with no fluff, but it is under-specified. It is not verbose, but its brevity sacrifices useful context.
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?
Though a simple tool with only 2 parameters and no output schema, the description is too minimal to be complete. It lacks explanation of the output structure, the meaning of 'unique', and how results are ordered or paginated.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema already provides 100% coverage with descriptions for both 'domain' and 'num', so the description adds no extra parameter semantics. The baseline of 3 applies since the schema does the heavy lifting.
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 'Get unique domain backlinks' clearly states the action (get) and the resource (unique domain backlinks), distinguishing it from siblings like get_domain_backlinks and get_unique_page_backlinks. However, it does not explain what 'unique' means precisely.
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 the similar get_domain_backlinks or get_unique_page_backlinks. Users are left to infer the difference from the name alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.