Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Get navigation

wordpress_get_navigation
Read-only

Retrieve a WordPress navigation post by ID with its raw block markup to inspect and plan edits, such as fixing href values in navigation-link blocks.

Instructions

[UNIFIED] Get a single wp_navigation post by ID, including its raw block-markup content. Use the returned content to plan an update_navigation call (e.g. fix href values inside blocks).

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>",
      "navigation_id": "<navigation_id>"
    },
    "name": "wordpress_get_navigation"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
navigation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.13.1

TDQS

A3.7/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile, and the description adds genuinely useful behavior beyond that: the response contains raw block markup rather than normalized fields, and it names the block comment syntax the content uses. It does not cover failure behavior for a bad or missing navigation_id, but the return-content characterization is the harder-to-guess detail and it is disclosed.

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?

Two sentences, front-loaded with the verb and resource, then the follow-up use case. Nothing is padded and the example syntax is directly actionable.

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

Completeness3/5

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

With no output schema, the description does well to specify the block-markup return type, but gaps remain around the site parameter and what happens when the navigation ID does not exist. For a simple two-parameter read tool it is mostly adequate.

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 the description carries the full burden. It only clarifies navigation_id implicitly via 'by ID'; the site parameter is never explained (slug, URL, or numeric ID?), and neither parameter is amplified in meaning.

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 pairs a specific verb (Get) with a specific resource (a single wp_navigation post by ID) and states what payload comes back (raw block-markup content). It stops short of naming a sibling to distinguish itself from, so an agent must infer the boundary against tools like wordpress_get_menu on its own.

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 gives concrete downstream context: use the returned content to plan an update_navigation call, with a worked example of fixing href values in navigation-link blocks. It offers no when-not guidance (e.g. when to prefer a menu or block specialist tool instead), but the primary use case is unambiguous.

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