Mark

Show Post

show_post

Read-onlyIdempotent

Use this when the person wants to see or review one post themselves: "show me the pricing post", "let's review this one". In Claude and ChatGPT it draws the post's preview with Approve, Request changes and Reject when it is in review, and its comments with a box to add one (comment_on_post); other clients get the same text as get_post. One post per call, and only for what the person asked to see. To read posts for a task (editing, checking media, approving, going through several), use get_post, which draws nothing. Related: get_post, search_posts, review_post.

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": "show_post"
  }
}

Input Schema

Name	Required	Description	Default
`postId`	Yes	The post id from search_posts or save_post.
`timezone`	No	IANA zone to render times in. Does not change stored data. Defaults to the workspace timezone.

Output Schema

Name	Required	Description	Default
`post`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already say readOnly/idempotent/non-destructive, and the description adds genuinely non-obvious behavior: client-dependent rendering (interactive preview with Approve/Request changes/Reject in Claude and ChatGPT, plain text via get_post elsewhere) and the inline comments box. Minor gap: it does not clarify that the preview's Approve/Reject controls are separate tools rather than effects of this call.

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?

Front-loaded with the use case and trigger examples before the rendering detail and the alternative. The client-behavior sentence is long and packs three ideas, but every clause carries distinct information; nothing is filler.

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 need not explain returns; it covers the pieces an agent actually needs — when to call it, what the person will see on each client, single-post scope, and which sibling to use for programmatic reading.

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 coverage is 100%, so postId provenance and the timezone caveat are already documented. The description adds only the 'one post per call' constraint and says nothing about timezone rendering, so it sits at the baseline.

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 first clause names a specific verb and resource ('see or review one post themselves') and immediately scopes it to a single post viewed by the person. It is unambiguously distinguished from get_post, which the description explicitly frames as the non-rendering read path.

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

Usage Guidelines5/5

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

It gives concrete trigger phrasing ('show me the pricing post', 'let's review this one') plus an explicit exclusion: for tasks like editing, checking media, approving, or going through several posts, use get_post. That is a full when/when-not/alternative statement.

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

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