Skip to main content
Glama
Rustysama

Postfjord

by Rustysama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

One idea to every format (drafts only)

postfjord_repurpose_idea

Turns one idea or blog URL into native social post drafts for up to 12 channels, an email draft, and an optional website section, then saves them for review without scheduling or sending.

Instructions

Use to spread one idea across every channel and email at once; for a single post, write it and save it with postfjord_create_draft. Turns one insight, or the address of a blog post, into a native post per channel, an email draft and optionally a website section, with Postfjord's AI (uses the workspace AI budget: one AI call for every 5 channels, run at the same time). Each post keeps the point in its own text, with no link-only teasers. The posts are saved as drafts, one per channel with a shared ideaGroupId, and the email as an email draft when email is on. Nothing is scheduled or sent: the person reviews the drafts in the app. Give idea, url, or both. At most 12 channels. If some channels come back in failed, the other drafts are saved: call again with the same ideaGroupId to write just those. Always send an ideaGroupId you make up (for example idea-20261001-breath); it is required for more than 5 channels, and send the same one again if the call fails (after a timeout, wait 2 minutes first: the call may still be writing), or to add more channels to the same idea: channels and the email that already have a draft in the group are not written or paid for twice.

Input Schema

NameRequiredDescriptionDefault
urlNoThe address of a blog post or article to start from.
ideaNoThe insight, tip or story, in the user's words.
pageNoAlso suggest a section for a website or landing page, returned as text.
emailNoAlso write an email draft (needs email switched on, see postfjord_mail_overview).
channelIdsNoIds from postfjord_list_channels to write a post for, at most 12.
ideaGroupIdNoYour own id for this idea, 8 to 64 letters, digits, _ or -. Required for more than 5 channels. Repeat it on a retry so nothing is made twice. After a timeout, wait 2 minutes before the retry.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Goes well beyond annotations (destructiveHint=false, idempotentHint=false): drafts only, nothing scheduled or sent, AI budget consumption (one AI call per 5 channels), a 12-channel cap, partial-failure behavior, and the timeout/2-minute-wait retry rule. It does not explain what the returned payload looks like, which is a minor gap.

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 purpose and the sibling contrast, and nearly every clause carries operational information. It is a single dense run-on paragraph with semicolon chains, which makes the retry and idempotency rules harder to scan than they should be.

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 needed, the description covers input choice, cost, concurrency, caps, partial failure, retry timing and idempotency, which is everything an agent needs to invoke this fan-out tool 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; the description earns more by adding semantics not in the schema, namely the de-duplication rule (channels and the email already having a draft in the group are not written or paid for twice) and a concrete ideaGroupId example. The 12-channel limit and the >5-channel requirement mostly restate the schema.

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 outcome ('spread one idea across every channel and email at once') and immediately contrasts it with the single-post sibling postfjord_create_draft. An agent can distinguish this fan-out tool from the create-draft tool 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it versus the alternative ('for a single post, write it and save it with postfjord_create_draft') and states the input condition ('Give idea, url, or both'). It also covers the retry path and the add-more-channels path with the same ideaGroupId.

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

Deploy Server

Other Tools