OnPage.dev

Backlinks

backlinks

Read-onlyIdempotent

Turn backlink data from Ahrefs, Semrush or similar into links won back, won or cleaned up. Pick with mode: broken = Broken and lost backlinks and 404 visits into 301s and outreach. Needs rows[{target_url, source_url, anchor, domain_rating, dofollow, http_code}]. opportunities = Sites linking to competitors, and unlinked brand mentions. Needs site. outreach = One outreach email per site, as drafts for the user's mail after approval. Needs your_site, prospects[{page, type, your_url, dead_url, anchor, contact}]. disavow = A conservative disavow.txt, only after a manual action or clear negative SEO. Needs rows[{url_from, domain, is_spam, domain_rating, anchor, traffic}], reason.

Input Schema

Name	Required	Description
`mode`	No	Default broken.
`rows`	No	Broken backlink rows, one per linking page.
`site`	No	Optional: your site's address.
`brand`	No	Brand name to look for in mention pages.
`yours`	No	Your own referring domains.
`detail`	No	brief = short summary.
`format`	No	Rule format, default redirects (Cloudflare Pages and Netlify _redirects).
`reason`	No	Why a disavow is considered.
`audit_id`	No	Optional: a finished site audit, to match on page titles too.
`mentions`	No	Pages that mention the brand.
`live_urls`	No	Optional: your live pages, instead of reading the sitemap.
`prospects`	No
`your_site`	No	Your site or brand name, e.g.
`memory_key`	No	site_memory key, records this call.
`competitors`	No	Each competitor with its referring domains.
`sender_name`	No	Name to sign with.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 14, 2026

removedOutput schema / description

Removed value: -"The result as structured data; fields depend on mode."

Changed2 schema fields changedOct 13, 2026

changedInput schema / properties / detail / description

Previous value: -"brief returns a short summary, default full."New value: +"brief = short summary."

changedInput schema / properties / memory_key / description

Previous value: -"Optional site_memory key, to record this call in the site memory."New value: +"site_memory key, records this call."

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / detail

Added value: +{
+  "description": "brief returns a short summary, default full.",
+  "enum": [
+    "full",
+    "brief"
+  ],
+  "type": "string"
+}

Changed1 schema field changedOct 12, 2026

addedInput schema / properties / memory_key

Added value: +{
+  "description": "Optional site_memory key, to record this call in the site memory.",
+  "maxLength": 80,
+  "type": "string"
+}

AddedOct 12, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so the safety profile is covered. The description still adds real behavior: outreach produces drafts that require user approval before use, and disavow is guarded by a caution about manual actions or negative SEO. It does not clarify that generated redirect/disavow files are not applied automatically to the site, which is the one trait worth surfacing.

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?

Front-loaded purpose followed by a compact mode-by-mode breakdown; each clause carries required inputs or a caution. The prose is dense and readable, though the array-literal notation is terse and slightly harder to scan than a structured list.

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

Completeness5/5

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

For a 16-parameter, four-mode tool with an output schema present, the description supplies the mode routing, per-mode required inputs, and the disavow caution. Nothing an agent needs to select and invoke the tool is missing, and return values are covered by the output schema.

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

Parameters4/5

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

Schema coverage is 94%, so the baseline is 3, but the description goes further by mapping modes to their required payloads (rows{target_url, source_url, anchor, domain_rating, dofollow, http_code}, prospects{page, type, your_url, dead_url, anchor, contact}, rows{url_from, domain, is_spam, ...}, reason). The schema declares all params optional at top level, so this per-mode requirement mapping is genuine added value.

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 states a specific transformation ('Turn backlink data ... into links won back, won or cleaned up') and the mode list names the four concrete jobs. It does not explicitly distinguish itself from the 'opportunities' sibling or find_opportunities, leaving a small ambiguity, but the verb+resource is clear.

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

Usage Guidelines5/5

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

The description gives explicit when-to-use guidance per mode: broken for lost links/404s, opportunities for competitor links and unlinked mentions, outreach for email drafts, disavow 'only after a manual action or clear negative SEO'. It also states the required inputs for each mode, which is exactly the routing information an agent needs.

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

All OnPage.dev tools Inspect

Try in Browser

Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.