Skip to main content
Glama
Sign In

Postmately

by com.postmately
OverviewDiscussionsAdmin

Create, schedule or publish a post

create_post

One post to one or more channels. when: "draft" saves it for review, "next_slot" puts it into the next free queue slot, "now" publishes right away, or an ISO 8601 date-time with a time zone schedules it. YouTube titles default to the first line of the text, visibility to Public. Publishing imported media does not spend credits.

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": {
      "channels": "<channels>",
      "when": "<when>"
    },
    "name": "create_post"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoPost text or caption
whenYes"draft", "next_slot", "now" or e.g. 2026-10-01T18:00:00Z
channelsYesChannel ids from list_channels, or { id, text, title, settings, mediaIds } for per-channel overrides. VK: settings { vkFormat: "clip" | "video" } picks VK Clips or a wall post for a video; photos and text go to the wall.
mediaIdsNoMedia ids from import_media

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful behavior beyond that: YouTube title defaulting to the first text line, default Public visibility, and the credit note for imported media. It does not disclose what happens on partial failure across multiple channels or what the call returns.

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?

Very compact and front-loaded: scope first, then the mode enumeration, then defaults and the credit note. The telegraphic fragment style ('One post to one or more channels') is slightly clipped but wastes no words.

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

Completeness3/5

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

For a multi-channel creation tool with no output schema, the description covers modes, defaults and cost but leaves the agent guessing about the response (post ids?) and about behavior when one of up to 50 channels fails. Adequate but not fully complete for a mutation with fan-out.

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%, so baseline is 3, but the description earns more: it explains that 'when' accepts a queue-slot keyword or an ISO 8601 date-time with a time zone, which sharpens the terse schema wording, and clarifies the YouTube title/visibility defaults that govern the per-channel 'title' and 'settings' fields.

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 opening line 'One post to one or more channels' plus the 'when' mode enumeration makes the verb and resource unambiguous: it creates/publishes a post across channels. It is distinguishable from delete_post, update_post and reschedule_post by implication (publish now vs. queue vs. draft), though it never names those siblings explicitly.

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?

The four 'when' values effectively give mode-selection guidance: draft for review, next_slot for queueing, now for immediate publishing, ISO 8601 for scheduled. This tells an agent which mode to pick. It stops short of stating when to use update_post or validate_post instead, or whether validation is recommended before publishing.

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

All Postmately 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