Skip to main content
Glama
Rustysama

Postfjord

by Rustysama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

AI compose (server side)

postfjord_ai_compose

Drafts channel-specific social text from a brief in your brand voice and returns it for review—nothing is saved. Use when you explicitly want Postfjord's built-in composer.

Instructions

Asks Postfjord's built-in composer to draft text per channel from a brief, in the brand voice, and returns the text only: nothing is saved (save it with postfjord_create_draft). To save a draft for every channel and an email from one idea in one call, use postfjord_repurpose_idea instead. Uses the workspace AI budget. Usually you can write the post yourself instead; use this when the user explicitly wants Postfjord's composer.

Input Schema

NameRequiredDescriptionDefault
toneNo
briefYes
channelsYes
mediaSummaryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already mark it non-read-only but non-destructive; the description adds key side effects: it returns text only, persists nothing, and consumes workspace AI budget. It does not detail budget limits or error behavior, but the main behavioral traits are disclosed.

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?

Four compact sentences, front-loaded with the core action and scoping, followed by alternatives and caveats. No wasted language.

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 no-output-schema tool, it explains that the return is text only and nothing is persisted, plus when to use it and that it consumes budget. The remaining gap is the unspecified shape of per-channel output and undocumented optional parameters, but core invocation needs are covered.

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

Parameters2/5

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

With 0% schema description coverage, the description must explain four parameters, but it only covers 'brief' and 'channels' at a high level. Optional 'tone' and 'mediaSummary' are not mentioned, and the channel object fields are left to the schema names.

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 gives a specific verb and resource ('draft text per channel from a brief') and immediately distinguishes the sibling paths: create_draft for saving and repurpose_idea for multi-channel plus email. An agent can select it 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?

It states when to use the tool (explicit user request for Postfjord's composer), when not to (usually write the post yourself), and names alternatives for saving and multi-channel repurposing. The routing guidance is explicit.

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