Skip to main content
Glama
Sign In
MCP Hub

MCP Hub

by airano-ir
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

WordPress: Wp blocks get

wordpress_specialist_wp_blocks_get
Read-only

Read a WordPress post or page as a structured block tree, fetching post_content via REST and parsing it into blockName, attrs, innerBlocks, and innerHTML entries.

Instructions

[UNIFIED] Read a post or page as a block tree. Fetches post_content via stock REST then parses it server-side with WP's block grammar so the caller gets a structured array of {blockName, attrs, innerBlocks, innerHTML} entries. Works on any WordPress 5.0+ install — no companion route needed for reads.

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_specialist_wp_blocks_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteYes
post_idYes
post_typeNoposts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.14.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the readOnlyHint annotation, the description explains that it fetches post_content via stock REST and parses it server-side with WordPress block grammar. It also documents the returned entry shape and compatibility with WordPress 5.0+, though it does not discuss auth, failure modes, or empty/malformed block handling.

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 front-loaded with the core action and then adds implementation and compatibility details without wasted wording. Every sentence contributes useful context.

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?

For a tool with no output schema, the description does well by describing the returned block-tree structure and the underlying fetch/parse behavior. However, the lack of parameter explanations is a meaningful completeness gap for a three-parameter tool.

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 needs to carry parameter meaning, but it does not explain site, post_id, or the post_type default. Only 'post or page' loosely hints at post_type, leaving the required site and post_id semantics undocumented.

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 gives a specific verb and resource: reading a post or page as a block tree. It is clearly a read operation, which distinguishes it from sibling block mutation tools such as insert, remove, and replace.

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?

The usage is implied by 'Read a post or page as a block tree,' and the note about no companion route helps frame when it works. However, it does not explicitly say when to choose this over other read tools like elementor_get, nor does it state exclusions.

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