Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Get internal links

wordpress_get_internal_links
Read-only

Extract internal links from a WordPress post's content, including anchor text and URLs, to analyze SEO internal linking and avoid duplicate links.

Instructions

[UNIFIED] Extract internal links from a post's content. Returns list of internal links with anchor text and URL. Useful for SEO internal linking analysis and avoiding duplicate links.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "site": "<site>",
      "post_id": "<post_id>"
    },
    "name": "wordpress_get_internal_links"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
post_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.13.1
    • addedInput schema / additionalProperties
      Added value: +false
  2. First observedv3.4.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description does add the return shape at a high level ("anchor text and URL"), but says nothing about truncation, pagination, whether external links are excluded, or how raw HTML is handled.

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?

Three short sentences, front-loaded with the action and the return value. The trailing SEO sentence is mildly promotional but does carry real intent information, so nothing is clearly wasted.

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

Completeness2/5

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

With no output schema and zero parameter descriptions, the description must carry the load, and it leaves the `site` format and post_id expectations unspecified. The brief return summary helps, but an agent could not reliably construct the call from this definition alone.

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

Parameters2/5

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

Schema description coverage is 0%, so both parameters depend on the description for meaning. It only indirectly implies post_id via "a post's content"; the `site` parameter (URL? key? ID?) is never explained, leaving half the input surface undefined.

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?

States a specific verb and resource: "Extract internal links from a post's content," which is plainly distinct from sibling readers like wordpress_get_post or wordpress_get_page. The only noise is the unexplained "[UNIFIED]" prefix, which adds no meaning to an agent.

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?

It names a use case ("SEO internal linking analysis and avoiding duplicate links") but never says when to pick this over alternatives or what preconditions apply (e.g., must the post exist, does it work on drafts). Usage is implied rather than directed.

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