Skip to main content
Glama

get_post

Read-only

Get one post written in DemandBird by its id: status, editorial stage, channels, the shared draft, each channel's own copy, media, tags, schedule or penciled time, author, the account each channel publishes from, first comments, every reviewer's status, and its sources' titles (never their text). An id you can't see, or that doesn't exist, returns "Post not found". Find ids with list_drafts, list_scheduled_posts or list_posts_awaiting_my_review. The post_id that search_posts, list_top_posts and get_post_analytics give is a different kind of id (a published post's); passed here it is looked up as a fallback, answering with its DemandBird post or saying it was made outside DemandBird. It has no performance numbers: for how a published post did, use get_post_analytics with that post_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": "get_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPost ID
workspaceNoOptional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / workspace
      Added value: +{
      +  "description": "Optional: the workspace (client) to answer from for this call only, by name (e.g. 'Acme') or numeric id, as returned by list_workspaces. Leave it out to use the current workspace. It does not change the current workspace; use select_workspace for that.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/destructive annotations, it discloses failure behavior ('Post not found' for invisible or nonexistent ids), a fallback lookup path for a different id type with its own answer ('made outside DemandBird'), and the privacy boundary that sources contribute titles but never text. This is exactly the extra context annotations cannot carry.

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 core action and a dense but purposeful field inventory that substitutes for the missing output schema. The long comma-separated field list in the opening sentence is heavy to parse, but nearly every clause carries decisions an agent would otherwise have to guess.

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 no output schema, the field enumeration is necessary and supplied; with two simple parameters fully covered, no param detail is owed. Edge cases (missing id, wrong id type, no metrics) are all addressed, leaving nothing an agent needs to call this correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it distinguishes DemandBird post ids from published-post ids and explains what happens on a cross-type lookup. It says nothing extra about the workspace parameter, though that parameter's own schema description already covers its scope and non-persistence.

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?

States a specific verb and resource ('Get one post written in DemandBird by its id') and then enumerates the fields returned, so an agent knows exactly what it gets. It is unmistakably distinct from list_* siblings and from get_post_analytics, which is named as the performance-numbers alternative.

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?

Explicitly routes the agent to list_drafts, list_scheduled_posts and list_posts_awaiting_my_review when it needs an id, and explicitly redirects to get_post_analytics when it needs performance data ('It has no performance numbers'). It also pre-empts the common mistake of passing a published post_id from search_posts, list_top_posts or get_post_analytics.

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