Skip to main content
Glama

Get post

get_post

Get one post by id: status (a scheduled post that was paused with pause_post reads paused; scheduledAt is kept), needsReschedule (true when the post was approved after its scheduled time, or is still unapproved past it: it will not auto-publish until the user picks a new time in the app; also per target), scheduledAt, publishedAt, permalink, platformPostId (null until published), approvalRequired and approval {required, approvedAt, approverName, changeRequestNote} (same shape as get_approval_status), Evergreen recycling settings (recyclingEnabled, recyclingIntervalDays, recyclingMaxRepeats, recyclingExpiresAt) and, per target (network), its channel, accountId, status, needsReschedule, platformPostId, permalink (link to the post on that network, null until published) publishedAt and deletedOnNetworkAt (ISO time the post was found deleted directly on that network, null otherwise; when set the permalink no longer works), failureReason and failureReasonCode (why that target failed to publish, e.g. ASPECT_RATIO; null unless it failed), plus its first comment (text, delayMinutes, status, permalink). A WORDPRESS target also carries a wordpress block: title, slug, excerpt, wpStatus, categoryIds, tagIds, featuredImage {url, alt} and the article body contentHtml, so an article can be read back before update_post. The post-level permalink is the Instagram one; use targets[].permalink for Threads and other networks.

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

Input Schema

NameRequiredDescriptionDefault
idYesThe post id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real system behavior: a paused scheduled post reads status=paused with scheduledAt retained, and needsReschedule means the post will not auto-publish until the user picks a new time in the app. It also specifies null semantics for platformPostId, permalink and deletedOnNetworkAt. It does not cover auth requirements or what happens when the id is unknown.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is correctly front-loaded in the first clause, but the rest is one extremely long run-on sentence enumerating dozens of fields inside nested parentheses. Much of the enumeration is necessary because there is no output schema, yet the dense single-sentence structure makes it hard to scan.

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 read tool with one parameter and no output schema, the description thoroughly documents the returned shape, including per-target fields, failure reasons, first comment, and the WORDPRESS-specific block. The notable gap is that it never states the behavior when the post id does not exist.

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?

There is a single parameter (id) at 100% schema coverage, so the schema already documents it and the description adds nothing about format or where ids come from (e.g., list_posts). This matches the baseline of 3 when the schema does the heavy lifting.

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 opening clause "Get one post by id" gives a specific verb (get), resource (post) and cardinality (one, by id), which naturally separates it from list_posts and from field-specific siblings like get_post_comments or get_post_metrics. It stops short of naming an alternative explicitly, so it is clear but not maximally differentiated.

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?

Usage is only implied: the WORDPRESS block is described as existing "so an article can be read back before update_post," which hints at a read-before-write workflow. There is no explicit statement of when to call this versus list_posts or get_post_comments, and no prerequisites or error conditions are given.

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