Skip to main content
Glama
Sign In

Postel

by app.postel
OverviewDiscussionsAdmin

Publish post now

publish-post
Destructive

Publish a Postel draft immediately to the social platform stored on the post. A post that is already published cannot be published again. 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. Before calling, show the user the exact text and the account it goes to, 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>"
    },
    "name": "publish-post"
  }
}

Input Schema

NameRequiredDescriptionDefault
postIdYesThe post ID to publish

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the destructive/openWorld annotations, it discloses idempotency behavior, plan-based quota enforcement, the failure mode (post remains a draft), and that the result reports remaining posts. These are exactly the operational traits an agent needs before firing an irreversible write.

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?

Four sentences, front-loaded with the action and destination, then constraints, then the pre-call confirmation rule. Slightly dense and the quota/fallback sentences overlap ('Past that, the post stays a draft and the result says so' restates the prior sentence), but nothing is wasted.

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?

No output schema exists, yet the description covers the return signal (remaining post count, draft-stayed outcome) and the irreversible nature of the call. For a single-parameter mutation tool, an agent has everything needed to invoke correctly.

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% for the single postId parameter, so the baseline is 3. The description adds meaning by noting the target platform is derived from the post rather than supplied, which clarifies that no destination parameter is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The first sentence states a specific verb and resource (publish a Postel draft) and pins the destination to the platform stored on the post. The word 'immediately' implicitly separates it from schedule-post, but no sibling is named outright, so differentiation is inferred rather than explicit.

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?

It gives an explicit precondition sequence: show the user the exact text and target account, then call only after confirmation. It also states a hard exclusion ('a post that is already published cannot be published again'), so both when-to-use and when-not-to-use are covered.

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