Postel

Schedule post

schedule-post

Destructive

Schedule a Postel draft for publishing to the social platform stored on the post. scheduledDateTime must be a future UTC ISO-8601 timestamp. A first comment can be set for LinkedIn posts. 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, the post is submitted for approval instead (status PENDING_APPROVAL) and an owner/admin must approve it in Postel. Before calling, show the user the exact text, the account it goes to and the time in their timezone, and call only after they confirm.

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": {
      "postId": "<postId>",
      "scheduledDateTime": "<scheduledDateTime>"
    },
    "name": "schedule-post"
  }
}

Input Schema

Name	Required	Description
`postId`	Yes	The post ID to schedule
`firstComment`	No	LinkedIn only: comment posted under the post right after it is published. Max 1250 characters.
`scheduledDateTime`	Yes	UTC ISO-8601 date string for when to publish (must be in the future)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

addedInput schema / properties / firstComment

Added value: +{
+  "description": "LinkedIn only: comment posted under the post right after it is published. Max 1250 characters.",
+  "maxLength": 1250,
+  "type": "string"
+}

First observedOct 1, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavior: future UTC timestamp requirement, LinkedIn-only first comment, plan-based scheduling limits with remaining count in the result, draft fallback when limits are exceeded, and approval submission with PENDING_APPROVAL status. These details materially help the agent predict outcomes.

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?

The description is front-loaded with the action and required timestamp constraint, then layers in plan, approval, and confirmation behavior without filler. Every sentence contributes operational context.

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?

For a consequential scheduling tool with no output schema, the definition covers prerequisites, timing format, plan limits, approval flow, and required user confirmation. The agent has enough information to invoke it correctly and explain likely outcomes.

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 the schema already documents all three parameters. The description reinforces that scheduledDateTime must be future UTC ISO-8601 and that firstComment is LinkedIn-only, but it adds limited meaning beyond the structured 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?

The description states a specific verb and resource: scheduling a Postel draft for future publishing to the social platform stored on the post. It distinguishes the action from immediate publishing through the scheduledDateTime requirement and sibling context.

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 gives clear pre-call guidance: show the user the exact text, target account, and localized time, and call only after confirmation. It also explains plan and approval conditions. It does not explicitly contrast this with publish-post, but the scheduling context is otherwise clear.

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

All Postel tools Inspect

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.