Postfjord

Publish now

postfjord_publish_now

Use only when the person wants a post live right now; otherwise give it a time with postfjord_schedule_post. Publishes a draft, scheduled, failed or partial post to all its channels immediately. Irreversible: the post goes live on the real accounts. Confirm with the user first. A video can take minutes; if the call times out, the post keeps publishing, so check it with postfjord_get_post. A retry with the same idempotency_key returns the first answer and never publishes twice. A publish that ended failed or partial is not kept, so after a fix the same call runs again.

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_publish_now"
  }
}

Input Schema

Name	Required	Description	Default
`postId`	Yes	A post id, from postfjord_list_calendar or postfjord_create_draft.
`idempotency_key`	No	Your own id for this one action, for example post-20261006-launch. Make a new one for each new thing; send the same one again only when you retry. Left out, the exact same call within 10 minutes counts as a retry.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 28, 2026
- addedInput schema / properties / postId / description
```
Added value: +"A post id, from postfjord_list_calendar or postfjord_create_draft."
```
First observedOct 26, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations only declare readOnly=false, openWorld=true, idempotent=false, destructive=false; the description adds the facts an agent actually needs: publishing is irreversible on real accounts, a video can take minutes, a timeout does not abort the publish, and the post should then be verified with postfjord_get_post. It also explains retry semantics that the annotations do not capture.

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 usage rule, then irreversibility, then timeout/retry edge cases — a sensible ordering. It is dense with zero filler, though the timeout, idempotency, and failure-retry sentences could be tightened into fewer clauses.

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?

For a two-parameter irreversible publish with no output schema, the description covers selection, confirmation, latency, timeout recovery, retry safety, and the failed/partial re-run case. Nothing an agent needs in order to call it safely is missing.

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 baseline is 3, and the description earns an extra point by explaining what idempotency_key actually guarantees ('returns the first answer and never publishes twice') beyond the schema's own wording. postId still gets no elaboration, since the schema already covers its source.

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 (publishes) and resource (a post) with explicit scope: 'a draft, scheduled, failed or partial post to all its channels immediately.' It distinguishes itself from the sibling it is not (postfjord_schedule_post) in the very first clause.

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?

Gives an explicit selection rule ('Use only when the person wants a post live right now; otherwise give it a time with postfjord_schedule_post') plus a prerequisite ('Confirm with the user first'). When-to-use, when-not, and the alternative are all named.

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?