Skip to main content
Glama

SEO Backlink Analysis

backlink_summary
Read-onlyIdempotent

Return a domain's backlink profile: domain rank, total backlinks, referring domains, spam score, and link distribution.

Related: whois.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "<domain>"
    },
    "name": "backlink_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesBare domain name such as example.com. No protocol (https://), path, or port; internationalized names in punycode (xn--...).

Output Schema

NameRequiredDescriptionDefault
cmsNo
rankNoDomain rank (0-1000 logarithmic scale)
errorNoError message when success is false
cachedNo
domainNo
serverNo
countryNo
successNo
backlinksNoTotal number of backlinks
first_seenNo
ip_addressNo
broken_pagesNo
crawled_pagesNo
referring_ipsNo
referring_pagesNo
broken_backlinksNo
referring_domainsNo
referring_subnetsNo
target_spam_scoreNoSpam score of domain itself (0-100)
referring_links_tldNoBacklink count by referring TLD
backlinks_spam_scoreNoSpam score of incoming backlinks (0-100)
external_links_countNo
internal_links_countNo
referring_links_typesNoBacklink count by link type (anchor, image, redirect, etc.)
referring_main_domainsNo
referring_pages_nofollowNo
referring_links_attributesNoBacklink count by link attribute (nofollow, sponsored, ugc, etc.)
referring_links_platform_typesNoBacklink count by platform type (blogs, news, ecommerce, etc.)
referring_main_domains_nofollowNo
referring_links_semantic_locationsNoBacklink count by semantic HTML location

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Domain name (no protocol or path)"New value: +"Bare domain name such as example.com. No protocol (https://), path, or port; internationalized names in punycode (xn--...)."
  3. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety and idempotency profile is fully covered by structured data. The description adds only the set of metrics returned, which is largely output-schema territory (an output schema exists), and says nothing about failure modes for malformed or nonexistent domains, data freshness, or rate limits. Useful but thin beyond the annotations.

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

Conciseness4/5

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

The metric list is front-loaded in the first sentence and nothing is padded or repeated. The trailing 'Related: whois' is a single short line, though it is the weakest part of the definition since it does not establish a routing rule.

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

Completeness3/5

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

For a one-parameter read-only tool with full schema coverage and an output schema, most of the burden is already carried by structured fields, so the definition is close to adequate. It is still silent on what happens when a domain has no backlink data or is invalid, and the vague 'Related: whois' line does not complete the picture of where this tool sits in the workflow.

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?

There is a single parameter and schema description coverage is 100%, with the schema itself specifying bare-domain format, no protocol/path/port, and punycode for internationalized names. The description adds no additional meaning about the domain argument, so this is the baseline case where the schema does all the work.

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 opens with a specific verb ('Return') and resource ('a domain's backlink profile') and enumerates the concrete metrics returned: domain rank, total backlinks, referring domains, spam score, link distribution. That is far more than a restatement of the name. It does not, however, distinguish the tool from anything else in a meaningful way; the only pointer is 'Related: whois,' which is a different data category rather than a competitive alternative.

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?

There is no when-to-use or when-not-to-use guidance. 'Related: whois' gestures at a neighbouring tool but never states the condition that would select one over the other, and no prerequisites, input preconditions, or exclusions are given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.