OnPage.dev

Internal links

internal_links

Read-onlyIdempotent

Internal links and link equity. Pick with mode: suggest = Links to add, with anchors, applied by Worker or CMS. Needs audit_id. equity = Internal PageRank and click depth from a site audit. Needs audit_id.

Input Schema

Name	Required	Description
`mode`	No	Default suggest.
`topic`	No	Topic or main keyword of the target page.
`detail`	No	brief = short summary.
`phrases`	No	Optional: phrases to turn into the link, besides the anchor text, for example natural variants.
`audit_id`	No	Id of a completed site audit.
`platform`	No	Optional: also return the links ready to apply: a Cloudflare Worker that links the first mention on each page, a WordPress edit plan, or the edits for the code.
`memory_key`	No	site_memory key, records this call.
`target_url`	No	Page that should receive links.
`important_urls`	No	Optional. Pages that matter most, for example top pages by clicks or revenue.

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

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context that suggested links can be 'applied by Worker or CMS', but says nothing about return format, cost, or limits beyond what annotations and the output schema provide.

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 content is front-loaded (topic statement first, then mode routing) and every phrase carries a distinct fact. It is terse and slightly telegraphic, but there is no redundant filler.

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

Completeness4/5

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

An output schema exists, so return values need not be described, and all 9 parameters are fully documented in the schema. The description supplies the mode-selection logic and audit_id prerequisite, leaving only minor gaps such as how the modes interact with the application-oriented params.

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 100%, so the baseline is 3, and the description earns above that by explaining the semantics of the mode enum (what 'suggest' and 'equity' actually return) and reaffirming the audit_id requirement, adding meaning beyond the schema's bare 'Default suggest.'

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 names the resource (internal links / link equity) and splits it into two concrete modes with their distinct outputs (links to add with anchors vs. Internal PageRank and click depth). This is specific enough for an agent to know what the tool produces, though it does not explicitly name which siblings it overlaps with.

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

Usage Guidelines4/5

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

The mode routing is explicit: 'suggest = Links to add...', 'equity = Internal PageRank and click depth', plus a stated prerequisite ('Needs audit_id') for both. This tells the agent when to pick each mode, but provides no guidance on when not to use the tool or which sibling to prefer instead.

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.