postnext

Test blog connection

test_blog_connection

Idempotent

Test connectivity to the team's connected WordPress blog (the PostNext plugin) and update the integration's health status. Returns whether the plugin is reachable + the token valid, plus the plugin version and capabilities. Pass integrationId when more than one blog is connected; otherwise the single connected blog is used. Business/Teams feature (a blog must be connected first).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "test_blog_connection"
  }
}

Input Schema

Name	Required	Description	Default
`integrationId`	No

Output Schema

Name	Required	Description	Default
`status`	Yes
`message`	No
`success`	Yes
`version`	No
`capabilities`	No
`integrationId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 2, 2026
- removedOutput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
First observedSep 22, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, and the description is consistent: it discloses that the call mutates state by updating the integration's health status, and that it verifies both plugin reachability and token validity. It adds gating context (Business/Teams, blog must exist first) that annotations don't convey, though it doesn't describe failure/rate-limit behavior.

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?

Three sentences, each earning its place: what it does and its side effect first, then the return payload, then the parameter rule and prerequisite. No filler and no repetition of the title.

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

Completeness5/5

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

With an output schema present, the description needn't enumerate return fields, yet it still summarizes the key ones (reachability, token validity, plugin version, capabilities). Prerequisites, side effects, and parameter semantics are all covered, so an agent has everything needed to call it correctly.

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

Parameters4/5

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

Schema coverage is 0%, so the description carries the burden, and it does explain the one parameter's role: integrationId selects a specific blog and is only needed when multiple blogs are connected, otherwise the sole connected blog is used. It doesn't state the expected ID format, but the cardinality semantics are clear.

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 states the specific verb and resource ('Test connectivity to the team's connected WordPress blog') and adds the notable side effect of updating the integration's health status, which sets it apart from every sibling tool (none of which perform a connection test). An agent can identify this as the health-check tool without inspecting the schema.

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 explicit prerequisites ('a blog must be connected first', Business/Teams feature) and states when to supply integrationId ('when more than one blog is connected; otherwise the single connected blog is used'). It stops short of naming an alternative or a when-not-to-call condition, which keeps it out of 5 territory.

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

All postnext 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?