Skip to main content
Glama

Get post

mynahcast_get_post
Read-onlyIdempotent

Get one post with its per-channel delivery state.

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

Input Schema

NameRequiredDescriptionDefault
postIdYes

Output Schema

NameRequiredDescriptionDefault
idYes
titleYes
originYes
statusYes
brandIdYes
targetsYes
approvalYes
createdAtYes
updatedAtYes
contentRevYes
contentHashYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / targets / items / properties / provider / enum
      Previous value: -[
      -  "bluesky",
      -  "mastodon",
      -  "telegram",
      -  "discord",
      -  "x",
      -  "linkedin",
      -  "youtube",
      -  "tumblr",
      -  "nostr",
      -  "lemmy",
      -  "misskey",
      -  "slack",
      -  "matrix",
      -  "devto",
      -  "hashnode",
      -  "wordpress",
      -  "listmonk"
      -]New value: +[
      +  "bluesky",
      +  "mastodon",
      +  "telegram",
      +  "discord",
      +  "x",
      +  "linkedin",
      +  "youtube",
      +  "tumblr",
      +  "nostr",
      +  "lemmy",
      +  "misskey",
      +  "slack",
      +  "matrix",
      +  "devto",
      +  "hashnode",
      +  "wordpress",
      +  "listmonk",
      +  "instagram",
      +  "threads",
      +  "facebook"
      +]
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds only the returning-data hint ('per-channel delivery state'), which is genuinely useful context, but says nothing about behavior for a missing or invalid post or about any delivery-state semantics.

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?

One short, front-loaded sentence with no filler; the retrieving verb and the notable detail (per-channel delivery state) lead. It is arguably too terse rather than too long, but nothing is wasted.

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

Completeness3/5

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

An output schema and rich annotations carry much of the burden, so the description need not explain return values. However, for a tool with three closely named siblings, the description does not explain the 'per-channel delivery state' notion or the error case for an unknown postId, leaving gaps an agent would want filled.

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 0%, but there is only one required parameter whose name (postId) plus uuid format and pattern are self-explanatory in the schema. The description adds no meaning beyond the schema, such as whether the ID may come from list_posts or whether invalid IDs error out; the single obvious param keeps this at an adequate 3.

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') and adds scope ('with its per-channel delivery state'), which separates it from a plain listing tool. It stops short of naming how it differs from the close sibling mynhcast_get_post_timeline, so the agent must infer the distinction.

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 explicit guidance on when to use this versus mynhcast_list_posts or mynhcast_get_post_timeline. The single-post scope is implied by 'one post', but there are no stated preconditions, exclusions, or alternative routing.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources