Skip to main content
Glama
intellieffect

Agentic CMS

by intellieffect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

send_to_postiz

Publish or schedule a content variant to a connected Postiz social channel, storing the Postiz post ID and creating a publication record on success.

Instructions

[Pipeline step 6 — Publish] Send a variant to Postiz for immediate or scheduled publication to the connected social channel. Typical flow: create_variant (step 4) → update_variant to fill body_text & hashtags → list_postiz_integrations → send_to_postiz. On success: variant.status becomes "sent_to_postiz", postiz_post_id is stored in platform_settings, and a publications row is automatically created. Use raw_payload to bypass the default DTO builder when a specific Postiz feature (media, thread, poll, etc.) is needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
forceNoIf true, send even when variant.status is already "sent_to_postiz". Default false — prevents accidental double-post.
channelNoChannel label for the publication record (e.g. "linkedin", "instagram"). If omitted, tries to infer from variant.platform.
dry_runNoIf true, builds the payload but does NOT call Postiz — useful for agent debugging.
variant_idYesVariant id to publish. variant.body_text will be used as the post content.
raw_payloadNoAdvanced: fully override the Postiz POST /posts body. If set, the tool sends this payload as-is (still records variant link + publication on 2xx).
scheduled_atNoISO 8601 timestamp to schedule the post. Omit for immediate publish.
integration_idYesPostiz integration id (channel). Get from list_postiz_integrations.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

No annotations provided, so the description carries full transparency burden and delivers: success state mutations (variant.status, platform_settings, publications row), the double-post prevention behavior, and the raw_payload override mechanism. Rich behavioral context for a mutation tool.

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 pipeline step designation and purpose, then flows into the typical flow, success effects, and the raw_payload caveat. Efficient but slightly dense with pipeline step numbering that partly restates the workflow.

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?

Complete for a mutation tool: names required prerequisites via the pipeline flow, discloses success side effects, documents the raw_payload escape hatch, and no output schema exists to explain. All an agent needs to call this correctly is present.

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 parameters are already documented, and the description reinforces the raw_payload bypass behavior. Adds context on how variant.body_text is used and where integration_id comes from, though doesn't add syntax beyond 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+resource ('Send a variant to Postiz') with scope ('immediate or scheduled publication'). Explicitly positioned as pipeline step 6 and distinguished from siblings like create_variant, update_variant, and list_postiz_integrations.

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 names the preceding pipeline steps (create_variant → update_variant → list_postiz_integrations → send_to_postiz) and states when to use raw_payload as an alternative to the default DTO builder. Nothing left to inference.

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