Alkemata Knowledge Gateway

Search website posts and pages

alkemata-search-published-content

Read-only

Search published WordPress posts or pages through the existing public MCP.

Input Schema

Name	Required	Default
`query`	No
`per_page`	No
`post_type`	No	post

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed14 schema fields changedOct 5, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / per_page / description
```
Removed value: -"Maximum results to return."
```
removedInput schema / properties / per_page / maximum
```
Removed value: -10
```
removedInput schema / properties / per_page / minimum
```
Removed value: -1
```
addedInput schema / properties / per_page / title
```
Added value: +"Per Page"
```
removedInput schema / properties / post_type / description
```
Removed value: -"Content type to search."
```
addedInput schema / properties / post_type / title
```
Added value: +"Post Type"
```
removedInput schema / properties / query / description
```
Removed value: -"Optional full-text search query."
```
addedInput schema / properties / query / title
```
Added value: +"Query"
```

addedInput schema / title

Added value: +"public_content_searchArguments"

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

removedOutput schema / properties

Removed value: -{
-  "items": {
-    "items": {
-      "additionalProperties": false,
-      "properties": {
-        "excerpt": {
-          "type": "string"
-        },
-        "id": {
-          "type": "integer"
-        },
-        "modified": {
-          "type": "string"
-        },
-        "title": {
-          "type": "string"
-        },
-        "type": {
-          "type": "string"
-        },
-        "url": {
-          "type": "string"
-        }
-      },
-      "required": [
-        "id",
-        "type",
-        "title",
-        "url",
-        "excerpt",
-        "modified"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "total": {
-    "type": "integer"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "total",
-  "items"
-]

addedOutput schema / title

Added value: +"public_content_searchDictOutput"

First observedSep 28, 2026

TDQS

C2.7/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the vague phrase 'through the existing public MCP', which hints at unauthenticated access but never states auth, rate limits, result ordering, or pagination behavior.

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?

A single front-loaded sentence with no filler, stating verb and resource immediately. It is efficient, though its brevity is partly the source of the missing detail rather than pure conciseness.

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?

An output schema exists so return values need not be explained, but with 0% schema coverage on three parameters and no usage or behavioral guidance, the definition is too thin for the agent to invoke it confidently with correct arguments.

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 for three parameters. It only vaguely covers 'query' and the post/page distinction (matching the post_type enum) and says nothing about per_page or the defaults, leaving two parameters unexplained anywhere.

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 (Search) and resource (published WordPress posts or pages), so the agent knows it is a search over published content. It does not explicitly contrast with the closest sibling, alkemata-get-published-content, but the search-vs-get distinction is reasonably inferable.

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 versus alternatives such as alkemata-get-published-content or search_topics, and no prerequisites or exclusions are given. Usage must be inferred entirely from the name and description.

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?