Skip to main content
Glama
postproxy

PostProxy MCP Server

Official
by postproxy

post_publish

Publish a post to specified social media profiles. Supports text, media attachments, scheduling, drafts, threads, and platform-specific customization.

Instructions

Publish a post to specified social media profiles. Supports text content, media attachments, scheduling, drafts, threads (X and Threads only), and platform-specific customization via the 'platforms' parameter.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
draftNoIf true, creates a draft post that won't publish automatically
mediaNoOptional array of media URLs or local file paths (images or videos). File paths can be absolute (/path/to/file.jpg), relative (./image.png), or use ~ for home directory (~/Pictures/photo.jpg)
threadNoOptional array of thread child posts (supported on X/Twitter and Threads only). The parent post is published first, then each child is published as a reply in order.
contentYesPost content text (caption/description)
profilesYesArray of profile IDs (hashids) or platform names (e.g., 'linkedin', 'instagram', 'twitter'). When using platform names, posts to the first connected profile for that platform.
queue_idNoOptional queue ID to add the post to. The queue will automatically assign a timeslot. Do not use together with 'schedule'.
scheduleNoOptional ISO 8601 scheduled time (e.g., '2024-12-31T23:59:59Z')
platformsNoPlatform-specific parameters. Keys are platform names, values are parameter objects. Use this to add collaborators, set video titles, privacy settings, etc.
queue_priorityNoOptional priority when adding to a queue (default: medium). Higher priority posts get earlier timeslots.
idempotency_keyNoOptional idempotency key for request deduplication
require_confirmationNoIf true, return summary without publishing (dry run)
Behavior4/5

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

Annotations already mark the tool as not read-only, not destructive, not idempotent, and open-world. The description adds context about supported features and platform-specific behaviors (e.g., thread support, scheduling, draft mode), which is valuable beyond the annotations. No contradictions are present.

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?

A single, well-structured sentence that efficiently conveys all key features without redundancy. Every phrase earns its place, making it easy to parse.

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?

Despite high complexity (11 parameters, nested objects, 12+ platforms), the description is comprehensive, covering primary use cases and important constraints (e.g., thread support limited to X/Threads, platform-specific parameters). No output schema exists, but the description does not need to detail return values.

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 description coverage is 100%, providing strong baseline semantics. The description adds value by summarizing high-level capabilities (drafts, scheduling, threads) and offering detailed platform-specific guidance in the 'platforms' parameter comment, exceeding schema details.

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 clearly states the tool's core function: 'Publish a post to specified social media profiles.' It lists specific supported features (text, media, scheduling, drafts, threads, platform-specific customization), efficiently distinguishing it from siblings like post_publish_draft, post_delete, etc.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description does not explicitly provide when-to-use or when-not-to-use guidance relative to alternatives. It lists capabilities, but the agent must infer usage context from sibling tool names (e.g., post_publish_draft for drafts). No exclusions or alternative recommendations are mentioned.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/postproxy/postproxy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server