Skip to main content
Glama
Sign In
wp-ssh-mcp

wp-ssh-mcp

by MSSOFTPC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

post_get

post_get
Read-onlyIdempotent

Retrieve a single WordPress post by its ID to inspect content, metadata, or status when managing a self-hosted site.

Instructions

Get one post by ID.

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": {
      "id": "<id>"
    },
    "name": "post_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPost ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, fully covering the safety profile. The description adds no behavioral context beyond restating a read operation, such as not-found behavior or scope of returned data.

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?

It is a single front-loaded sentence with no filler. Every word, including 'one', contributes to scope and action.

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

Completeness4/5

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

For a simple one-parameter read tool with 100% schema coverage and full read-only annotations, the description is nearly complete. It could still mention the return shape or lookup alternatives, but the missing pieces are minor for this complexity level.

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

Parameters3/5

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

Schema description coverage is 100%, so the single required 'id' parameter is already documented in the schema as the post ID. The description restates 'by ID' but adds no syntax or format details beyond the schema.

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 states a specific verb and resource: 'Get one post by ID.' The word 'one' distinguishes it from the sibling post_list, though it does not explicitly name post_list or other retrieval alternatives.

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 phrase 'by ID' implies the tool is used when a post ID is known, which is minimal implied guidance. It does not say when to prefer post_get over post_list or other lookup siblings, nor does it mention exclusions or prerequisites beyond the ID.

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