Skip to main content
Glama
Sign In

Postel

by app.postel
OverviewDiscussionsAdmin

Create posts in bulk

create-posts
Destructive

Create up to 25 posts in one call. Each post is saved as a draft; a post with scheduledDateTime is then scheduled for publishing to its platform. Scheduling and publishing depend on the account's Postel plan; a workspace without one can schedule or publish a limited number of posts, and the result says how many are left. Past that, the post stays a draft and the result says so. If the workspace requires approval, a dated post is submitted for approval instead (status PENDING_APPROVAL) and an owner/admin must approve it in Postel. Posts are processed in order with one result each, so some can succeed while others fail. At most 25 media URLs per call.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "posts": "<posts>"
    },
    "name": "create-posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
postsYesPosts to create, in order

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / posts / items / properties / platform / description
      Previous value: -"Destination platform: \"x\" (default), \"linkedin\", \"bluesky\" or \"mastodon\""New value: +"Destination platform: \"x\" (default), \"linkedin\", \"bluesky\", \"mastodon\", \"youtube\" or \"tiktok\""
  2. Changed1 schema field changed
    • changedInput schema / properties / posts / items / properties / platform / enum
      Previous value: -[
-  "x",
-  "linkedin",
-  "bluesky",
-  "mastodon"
-]New value: +[
+  "x",
+  "linkedin",
+  "linkedin_page",
+  "bluesky",
+  "mastodon",
+  "threads",
+  "youtube",
+  "instagram",
+  "tiktok"
+]
  3. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare write/openWorld/destructive; the description goes far beyond them by disclosing draft-by-default behavior, plan-dependent scheduling limits with remaining-count feedback, the owner/admin approval requirement, and partial-failure semantics ('processed in order with one result each, so some can succeed while others fail'). It also adds a cross-post cap of 25 media URLs per call that is not visible from the per-post schema.

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?

Six sentences, front-loaded with the action and size limit, then progressively covering scheduling, plan limits, approval, and ordering. Every sentence carries information, though the plan/approval sentences are dense and could be split for faster scanning.

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?

With no output schema, the description does the work of explaining that results come back one-per-post and can be mixed success/failure, plus the draft-versus-scheduled outcome rules. It doesn't describe what a result entry actually contains or error shapes for validation failures, which is the remaining gap.

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 field-level meaning (content, platform, mediaUrls, firstComment, scheduledDateTime) is already documented in the schema. The description only adds the aggregate 25-media-URL cap and the omit-scheduledDateTime-keeps-draft rule, both marginal additions, so the baseline 3 applies.

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 opens with a specific verb plus resource and explicit bulk scope ('Create up to 25 posts in one call'), which cleanly separates it from the sibling create-post and the publish/schedule tools. An agent can tell which tool to pick without opening the schema.

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

Usage Guidelines4/5

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

It states the conditional paths clearly: draft by default, scheduled when scheduledDateTime is present, submitted for approval when the workspace requires it, and left as a draft when plan limits are exhausted. It does not explicitly name create-post as the single-post alternative or list when-not-to-use cases, which keeps it below a 5.

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

All Postel toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources