Postfjord

Get post

postfjord_get_post

Read-only

One post with its per-channel status, permalinks and errors, and each channel's picture shape (aspect) and fit. To see the pictures themselves, use postfjord_preview_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": "postfjord_get_post"
  }
}

Input Schema

Name	Required	Description	Default
`postId`	Yes	A post id, from postfjord_list_calendar or postfjord_create_draft.

Output Schema

Name	Required	Description
`id`	No
`status`	No
`targets`	No	Per channel id: its text, status, permalink and error.
`baseText`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 28, 2026

addedInput schema / properties / postId / description

Added value: +"A post id, from postfjord_list_calendar or postfjord_create_draft."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "baseText": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "status": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "targets": {
+      "additionalProperties": {},
+      "description": "Per channel id: its text, status, permalink and error.",
+      "properties": {},
+      "type": "object"
+    }
+  },
+  "type": "object"
+}

First observedOct 26, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description still adds value by disclosing the payload shape (status, permalinks, errors, per-channel aspect and fit), which tells the agent this call surfaces failure information per channel — a behavioral fact not in 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?

Two short sentences, payload description front-loaded, routing sentence second. No filler, no restatement of the tool name or title.

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?

With annotations covering safety, a full output schema, and a documented single parameter, the description needs only to explain what the call returns and when to prefer the sibling — which it does. The one small gap is no mention of behavior when the post id is unknown (not-found handling).

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 with 100% schema description coverage, and the schema already states the pattern and where the id comes from (list_calendar or create_draft). The description adds no further meaning about postId, so the baseline 3 applies.

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 names a specific verb/resource (fetch one post) and enumerates its payload: per-channel status, permalinks, errors, and each channel's aspect and fit. It also explicitly distinguishes itself from postfjord_preview_post, so an agent can pick between the two without opening either schema.

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 when-not case is explicit and routed: 'To see the pictures themselves, use postfjord_preview_post.' What's missing is a positive trigger (e.g. after list_calendar or create_draft to inspect publishing state) and any prerequisite/scope notes, so it stops short of a full when/when-not/alternatives statement.

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

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