Alkemata Knowledge Gateway

Read a website post or page

alkemata-get-published-content

Read-only

Read a published WordPress post or page through the existing public MCP.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`post_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 5, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / post_id / description
```
Removed value: -"Numeric WordPress post or page ID."
```
removedInput schema / properties / post_id / minimum
```
Removed value: -1
```
addedInput schema / properties / post_id / title
```
Added value: +"Post Id"
```

addedInput schema / title

Added value: +"public_content_getArguments"

changedOutput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

removedOutput schema / properties

Removed value: -{
-  "content_text": {
-    "type": "string"
-  },
-  "excerpt": {
-    "type": "string"
-  },
-  "id": {
-    "type": "integer"
-  },
-  "modified": {
-    "type": "string"
-  },
-  "published": {
-    "type": "string"
-  },
-  "title": {
-    "type": "string"
-  },
-  "type": {
-    "type": "string"
-  },
-  "url": {
-    "type": "string"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "id",
-  "type",
-  "title",
-  "url",
-  "excerpt",
-  "content_text",
-  "published",
-  "modified"
-]

addedOutput schema / title

Added value: +"public_content_getDictOutput"

First observedSep 28, 2026

TDQS

B3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds one useful behavioral constraint — only published content is retrievable — but says nothing about behavior for unpublished/invalid IDs or permissions. 'Through the existing public MCP' adds no actionable context.

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?

One short, front-loaded sentence with the verb first. The trailing clause 'through the existing public MCP' is filler that does not help an agent decide or invoke, keeping it just short of a 5.

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?

An output schema exists, so return values need not be described, and the tool is a simple read-only single-parameter lookup. Still, the post-vs-page distinction and the meaning of post_id are left entirely unaddressed, leaving a gap the schema does not fill.

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% and the single required parameter post_id has no title-level explanation. The description only implies that some identifier of a post or page is needed, without clarifying whether it is a WordPress post ID, how pages vs posts are resolved, or what an invalid ID yields.

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+resource: 'Read a published WordPress post or page'. The singular phrasing and 'get' name distinguish it from the sibling 'alkemata-search-published-content', though the description never explicitly names that sibling or contrasts itself with it.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool, when not to, or which sibling handles the search case. The word 'published' weakly implies drafts are out of scope, but the agent receives no routing guidance at all.

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

All Alkemata Knowledge Gateway tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?