Skip to main content
Glama
sparrow84001

SEO, AEO, GEO & Digital Marketing Audit + Safe Fix MCP Server

by sparrow84001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

seo_audit_internal_links

Audit internal linking to detect generic anchors, orphan pages, and weak topic clusters. Receive contextual link suggestions that improve PageRank flow and anchor relevance.

Instructions

Audits internal linking structure, identifies generic anchor text ('click here', 'read more'), flags orphan pages, and suggests high-value contextual links between blog articles and service pages.

USAGE GUIDELINES:

  • Use to improve PageRank flow, internal topic clustering, and anchor text relevance across pages.

  • Do NOT use to inspect external backlink profiles; use 'seo_suggest_related_ecosystem' for off-page targets.

BEHAVIORAL TRANSPARENCY:

  • Safe, read-only link graph analysis. No file modifications.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
targetYesTarget live URL (e.g. "https://example.com") or local file path to audit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • changedInput schema / properties / target / description
      Previous value: -"Target file path or live URL."New value: +"Target live URL (e.g. \"https://example.com\") or local file path to audit."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It explicitly states 'Safe, read-only link graph analysis. No file modifications,' directly informing the agent that invocation has no side effects. This is strong transparency for a tool with no annotation metadata.

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?

Three short labeled sections front-load the main purpose and place usage and safety notes in scannable bullets. Every sentence earns its place, with no redundancy or filler.

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 one-parameter, read-only audit tool, the description covers what it does, when to use it, what not to use it for, and its safety profile. The described artifacts (generic anchor text, orphan pages, suggested links) set clear expectations even without an output schema.

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 coverage is 100% and the schema already describes target as a live URL or local file path. The description reinforces that the target is the subject of an internal-link audit but does not add new parameter-level meaning such as format constraints, defaults, or additional usage examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb-resource pair ('Audits internal linking structure') and lists concrete outputs (generic anchor text, orphan pages, link suggestions), making it clearly distinct from the many seo_audit_* siblings. Even without naming each sibling, the internal-link focus is unambiguous.

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?

Explicit usage bullets state when to use the tool ('to improve PageRank flow, internal topic clustering, and anchor text relevance') and when not to use it ('Do NOT use to inspect external backlink profiles'). It directly names seo_suggest_related_ecosystem as the alternative for off-page targets, leaving no ambiguity about routing.

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

Deploy Server

Other Tools