Skip to main content
Glama

CorpusIQ

by io.corpusiq
OverviewDiscussionsAdmin

Ahrefs Connector

ahrefs_connector
Read-onlyIdempotent

Ahrefs SEO platform: domain rating, backlink analysis, organic keywords, referring domains, competitor research, top pages by traffic, and keyword research. When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesget_domain_overview: Get a combined domain authority, backlink, and organic traffic overview from Ahrefs for a given domain. Returns Domain R | get_organic_keywords: Get the top organic (SEO) keywords that a domain ranks for in Ahrefs. Returns keyword, ranking position, monthly search | get_backlinks_overview: Get a backlink profile summary for a domain from Ahrefs. Returns live backlink count, live referring domain count, all-t | get_refdomains: Get a list of referring domains linking to a given domain, from Ahrefs. Returns each referring domain with its Domain Ra | get_competitors: Get organic competitor domains for a given domain from Ahrefs. Returns domains that compete for the same organic keyword | get_top_pages: Get the top-performing pages for a domain ranked by organic traffic, from Ahrefs. Returns each page's URL path, estimate | get_keyword_overview: Get keyword research data from Ahrefs for a specific keyword or phrase. Returns monthly search volume, keyword difficult
paramsNoAction-specific parameters. get_domain_overview: {domain: string} | get_organic_keywords: {domain: string, country?: string, limit?: integer} | get_backlinks_overview: {domain: string} | get_refdomains: {domain: string, limit?: integer} | get_competitors: {domain: string, country?: string, limit?: integer} | get_top_pages: {domain: string, country?: string, limit?: integer} | get_keyword_overview: {keyword: string, country?: string}

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the bar is lower, and the description adds genuine behavioral traits: the 15-minute, any-replica provenance receipt and the verified vs unverified_model_data distinction for downstream rendering. It does not cover auth requirements, rate limits, or error behavior of the connector itself.

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?

Roughly two-thirds of the text concerns chart_render's calling convention, provenance tokens, attribution footers, and the accuracy contract rather than this tool's own invocation. The actual purpose is front-loaded, but the bulk is off-topic bloat that dilutes the signal for selecting and calling this connector.

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 seven-action connector with no output schema, the description explains the data domain and downstream contracts but does not say which action answers which question or what each returns beyond the truncated schema text. It is adequate but leaves selection among its own actions to inference.

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?

Schema description coverage is 100%, so the enum descriptions and per-action params object already document every field (domain, country, limit, keyword). The description adds no syntax, default, or format detail beyond the schema, so the baseline 3 applies.

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 opening sentence names the platform and enumerates the concrete SEO resources it covers (domain rating, backlinks, organic keywords, referring domains, competitors, top pages, keyword research), which map one-to-one onto the action enum. An agent can tell it is the SEO data connector, though it never explicitly contrasts itself with the sibling semrush_connector or ahrefs_dashboard.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives extensive procedural guidance about downstream steps (when to call chart_render, passing provenance_token, appending the attribution footer, the data-accuracy contract), but says nothing about when to choose this connector over semrush_connector or ahrefs_dashboard, nor which action to pick for a given question. Usage is implied through the token/downstream rules rather than explicit tool-selection criteria.

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

All CorpusIQ toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources