Skip to main content
Glama
newilu

ahrefs-mcp

by newilu

Backlinks stats

backlinks-stats

Analyze a domain's backlink profile by retrieving live and all-time backlinks and referring domains.

Instructions

Backlink footprint of a domain: live and all-time backlinks and referring domains.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesDomain or URL to analyze, e.g. example.com
Behavior3/5

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

With no annotations, the description carries the full transparency burden. It discloses the temporal scope (live vs. all-time), which is useful, but does not mention data update frequency, limitations, or whether results are aggregated or raw. This is a minimal but non-trivial disclosure.

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

Conciseness5/5

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

The description is a single concise sentence that front-loads the key purpose. It contains no unnecessary words or repetition, making it optimally scannable.

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 simple one-parameter tool, the description covers the core outputs (backlinks, referring domains) and adds the live/all-time distinction. However, without an output schema or annotations, it leaves the agent uncertain about the exact response shape, so it is adequate but not fully complete.

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 schema already fully describes the single 'target' parameter with an example. The description adds no additional parameter context, so the baseline score of 3 applies given 100% schema coverage.

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 tool's output (backlink footprint with live and all-time backlinks and referring domains). It is specific about the data delivered, but does not explicitly differentiate from sibling tools like 'referring-domains'.

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 given on when to use this tool versus alternatives. The description only defines the tool's function without context about complementary or competing tools, leaving usage decisions entirely to the agent.

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/newilu/ahrefs-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server