Notipo

Get Post

get_post

Read-only

Get details of a specific post by ID, including status, WordPress URL, and category.

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": {
      "postId": "<postId>"
    },
    "name": "get_post"
  }
}

Input Schema

Name	Required	Description	Default
`postId`	Yes	The post ID

Output Schema

Name	Required	Description
`id`	Yes
`title`	Yes
`wpUrl`	Yes
`status`	Yes	DRAFT \| PUBLISHED \| SYNCED \| FAILED, etc.
`category`	Yes
`wpPostId`	Yes
`createdAt`	Yes
`updatedAt`	Yes
`notionPageId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 19, 2026

TDQS

A4.1/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, covering the safety profile. The description adds that the response includes status, WordPress URL, and category, but it does not disclose additional behavioral traits such as error conditions or authorization requirements. Nothing contradicts the annotations.

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?

A single, front-loaded sentence states the operation, the target, and the key returned fields with no filler or redundant wording.

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?

This is a simple one-parameter read-only lookup with an output schema and safety annotations. The description is sufficient for an agent to select and invoke the tool correctly without missing information.

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?

The schema provides 100% coverage: postId is described as 'The post ID'. The description's 'by ID' matches the parameter but adds no meaningful semantic detail beyond what the schema already states.

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 clearly identifies the action ('Get'), the resource ('specific post'), and the retrieval key ('by ID'). It also names the meaningful return fields, which distinguishes it from listing tools like list_posts.

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?

The phrase 'specific post by ID' provides a clear usage context: use this when you need one known post's details rather than a list. It does not explicitly name alternatives or exclusion conditions, but the context is unambiguous.

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

All Notipo 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.