Skip to main content
Glama

PostWire

by io.github.Perufitlife
OverviewDiscussionsAdmin

Set up a recurring post

create_recurring_post

Sets up a post that repeats on a schedule: daily, weekly on some weekdays, or monthly on some days of the month (31 falls on the last day of shorter months; -1 = the last day), every N days, weeks or months, at 1-4 times a day in a timezone (daylight saving handled), from a start date until an end date or for a number of times. variants (a list of texts) are used in turn, so the same text does not repeat every time. The duplicate guard (guard_days, default 3, 0 = off) skips a network where the same text went out in the last guard_days when an occurrence is published: networks flag repeated posts. Occurrences are put in the queue up to 7 days ahead as ordinary scheduled posts (each can be edited or canceled alone), and go through the brand's approval rules and the plan's limits like any post. On every paid plan (Starter 25, Pro 100, Agency 500, Scale 2,000 at a time); not on Free. Returns the recurring post with its next occurrences and any warnings (for example: one text every day with a 3-day guard would be skipped).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ruleYesWhen it repeats.
textNoThe post, when there is one text.
labelNoName shown in the queue, e.g. "Monday tip".
brand_idNoBrand whose accounts to use; omit for the default brand.
variantsNoTexts used in turn: the 1st occurrence uses the 1st, the 2nd the 2nd, and so on, starting again after the last.
photo_urlNoOptional image (public https link).
platformsYesConnected platforms to post to.
video_urlNoOptional video (public https link).
guard_daysNoSkip a network where the same text went out in the last N days. Default 3; 0 = off.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / platforms / items / enum
      Previous value: -[
-  "telegram",
-  "bluesky",
-  "mastodon",
-  "discord",
-  "tiktok",
-  "youtube",
-  "reddit",
-  "linkedin",
-  "facebook",
-  "instagram",
-  "x"
-]New value: +[
+  "telegram",
+  "bluesky",
+  "mastodon",
+  "discord",
+  "wordpress",
+  "devto",
+  "hashnode",
+  "slack",
+  "nostr",
+  "tiktok",
+  "youtube",
+  "reddit",
+  "linkedin",
+  "facebook",
+  "instagram",
+  "x"
+]
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Annotations only state readOnly=false, destructive=false, idempotent=false, openWorld=true; the description goes far beyond that, disclosing DST handling, the duplicate guard and its default/off behavior, that occurrences are queued up to 7 days ahead as editable/cancelable posts, that they flow through brand approval rules and plan limits, and that the call returns warnings. This is exactly the mutation context an agent needs.

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?

It is a single dense paragraph, but nearly every clause carries unique behavior (guard, queue, plans, returns). Front-loaded with purpose before the mechanics. Slightly less scannable than it could be as one long run-on, but no filler sentences.

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 9-parameter mutation tool with nested objects and no output schema, the description covers inputs, side effects, plan gating, and the return shape ('the recurring post with its next occurrences and any warnings'), including an example warning. Nothing an agent needs to invoke it correctly is missing.

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 adds real meaning beyond the schema: it explains the guard_days skip semantics with a worked edge case, the 31/-1 month-day fallback, the round-robin use of variants, and DST-aware timezone handling. These clarify how parameters interact at runtime rather than just restating field docs.

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?

States a specific verb and resource ('Sets up a post that repeats on a schedule') and immediately scopes it to recurring behavior, distinguishing it from one-off siblings like schedule_post and bulk_schedule. The recurrence taxonomy (daily, weekly, monthly, every N) makes the tool's remit unambiguous.

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

Usage Guidelines3/5

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

It gives rich operating context (paid-plan requirement with tier limits, Free exclusion, queue/approval behavior) but never explicitly says when to prefer this over schedule_post or bulk_schedule, nor does it name an alternative. Usage is strongly implied rather than routed.

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

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