Skip to main content
Glama
alokemajumder

wpxmcp

by alokemajumder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Internal link report

internal_link_report
Read-only

Identify internal linking issues in WordPress content: find orphans, dead ends, links to non-public posts, and suggest related content pairs that lack links. Read-only analysis based on content bodies.

Instructions

Build the internal link graph across published content and report orphans (nothing links to them), dead ends (they link to nothing), links pointing at drafts/private/trashed items, and link suggestions: related pairs (shared categories/tags and title keywords) with no link between them. Read-only — suggestions only; add links with update_content. Based on content bodies, so menu, widget and archive links are not counted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum published items to load across all types (most recent first). The graph is only as complete as this.
typesNoContent types to include in the graph.
site_idNoWhich configured WordPress site to act on. Optional — with a single site configured it is used automatically; with several, the default site is used unless you name one. Run list_sites for valid ids.
max_rowsNoMaximum rows in each list (orphans, dead ends, and so on).
max_suggestionsNoHow many link suggestions to return.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark readOnlyHint and destructiveHint false, but description adds more: it's based on content bodies, ignores menus/widgets, and gives suggestions only. That's valuable behavioral context beyond the annotations.

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 compact yet dense, covering all important aspects in two sentences without fluff. Key purpose is front-loaded.

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 an analysis tool with no output schema, the description fully explains what it returns (categories of issues), scope, limitations, and side effects (none). No critical missing info.

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 has 100% coverage with detailed descriptions for each parameter (limit, types, site_id, max_rows, max_suggestions). The description adds little about parameters, but it does imply the purpose of the graph. Baseline 3 is appropriate.

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 clearly states it builds an internal link graph and reports specific categories of issues (orphans, dead ends, links to drafts, suggestions). It distinguishes from a generic content tool and clearly defines scope.

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?

It explains when to use (for link analysis), what it doesn't count (menu, widget, archive links), and read-only nature. It references update_content for creating links, but doesn't explicitly say when not to use it or mention alternatives.

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