Skip to main content
Glama
postoria-app

Postoria MCP Server

Official
by postoria-app

publish_post_now

Create and publish a post to social accounts instantly with specified content, media, and settings via the Postoria API.

Instructions

Create and publish a Postoria post immediately.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspace_idYesPostoria workspace ID.
social_account_idsYesOne or more Postoria social account IDs to publish to.
content_typeNoOptional content type. If omitted, Postoria will infer it from media/link/caption.
media_idsNoMedia IDs already created or imported through the Postoria Public API.
captionNoPost caption text.
link_urlNoOptional link URL for link posts.
first_commentNoOptional first comment.
comment_delayNoOptional first comment delay, in minutes.
repostNoOptional repost/recycle settings.
youtubeNoOptional YouTube-specific settings.
tiktokNoOptional TikTok-specific settings.
Behavior2/5

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

No annotations provided. The description only notes 'immediately' but discloses no other behavioral traits such as potential destructive actions, prerequisites (e.g., media upload), or rate limits.

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?

Single sentence, zero wasted words, front-loaded with the key action.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite 11 parameters including nested objects and no output schema, the description provides minimal context. It does not mention required parameters or optional features, leaving the agent underinformed.

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

Parameters3/5

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

Schema coverage is 100%, so baseline is 3. The description adds no parameter-specific meaning, but the schema itself is detailed.

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 action: 'Create and publish a Postoria post immediately.' It uses a specific verb-resource pair and distinguishes from scheduling tools.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus siblings like schedule_post or add_post_to_queue. The implied usage is for immediate publishing, but explicit context is missing.

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/postoria-app/postoria-mcp-server'

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