Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Post Schedule

post_schedule

Schedules new or draft social media posts for publication at a chosen time across selected channels, including approval waits when required.

Instructions

Schedule a social media post for a time: a new post from content and channelIds, or an existing draft (postId; content, channelIds or targets and media then replace its text, channels and media). It is published at that time unless someone changes it in FirstReply. When the organization requires approval, a member's post waits for a manager (status PENDING_APPROVAL).

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": {
      "organizationId": "<organizationId>",
      "scheduledAt": "<scheduledAt>"
    },
    "name": "post_schedule"
  }
}

Input Schema

NameRequiredDescriptionDefault
mediaNoImages or videos of the post, in order, uploaded with post_media_upload. Instagram, TikTok and YouTube need media; what each channel accepts is checked when the post is saved.
postIdNoAn existing post to schedule. Omit to create a new post.
contentNoThe text of the post. Required for a new post.
targetsNoThe channels to post to with their own text or platform settings, instead of channelIds; only channels with publishingEnabled (see channel_list). Settings by channel type: INSTAGRAM: postType FEED (default), REELS or STORY; shareToFeed (Reels, default true). X: threadParts, the texts of the posts after the first one of a thread. YOUTUBE (one video): title (required, up to 100 characters), madeForKids (required, true or false), format VIDEO or SHORT, privacyStatus public, unlisted or private, categoryId, containsSyntheticMedia. The text is the description. TIKTOK: privacyLevel (required, one the account offers, see channel_tiktok_creator_info), allowComment, allowDuet, allowStitch, commercialContent with yourBrand and/or brandedContent, title (photo posts), and musicUsageConfirmed true (required) plus brandedContentPolicyConfirmed true for branded content: set these two only after the user agreed to TikTok's Music Usage Confirmation and Branded Content Policy. GOOGLE_BUSINESS: topicType STANDARD, EVENT or OFFER; actionType NONE, BOOK, ORDER, SHOP, LEARN_MORE, SIGN_UP or CALL with actionUrl; events and offers: eventTitle, startDate and endDate (YYYY-MM-DD), startTime and endTime (HH:mm); offers: couponCode, redeemUrl, terms. MASTODON: visibility public, unlisted or private; spoilerText (content warning). TELEGRAM: silent (no notification).
timezoneNoIANA time zone the post is planned in, e.g. Europe/Vienna. Shown in the calendar.
channelIdsNoIds of the channels to post to; only channels with publishingEnabled (see channel_list). Required for a new post, unless targets are given.
scheduledAtYesWhen to publish: ISO 8601 date-time with UTC offset, e.g. 2026-11-10T10:00:00+01:00. At least 10 minutes from now.
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4/5.0
Behavior4/5

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

Beyond the annotations, it discloses real behavioral traits: the post publishes at the scheduled time unless edited in FirstReply, drafts get their text/channels/media overwritten, and approval-required orgs leave member posts in PENDING_APPROVAL. The overwrite-on-draft behavior is especially valuable since destructiveHint=false and idempotentHint=false alone would not warn an agent about replacement semantics.

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?

Three sentences, front-loaded with the core action and the two modes, then the publish/approval caveats. Dense but every clause carries new information; minor awkwardness in the parenthetical draft-override phrasing.

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?

For an 8-parameter, 100%-covered mutation schema with no output schema, the description supplies what the schema cannot: mode selection, publish timing, draft override, and approval outcome. Return shape and scheduling failure modes are not described, but no output schema exists to defer to, leaving a small gap.

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 the baseline is 3, but the description adds relational meaning the schema cannot: that content/channelIds are required for a new post unless targets are given, and that these fields replace the draft's values. That clarifies parameter interplay for the two operating modes rather than restating field descriptions.

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 description names a specific verb and resource ('Schedule a social media post for a time') and covers both input modes: creating a new post from content/channelIds and scheduling an existing draft via postId. It does not differentiate itself from siblings like post_reschedule or post_create, so the agent must infer whether rescheduling a scheduled post belongs here.

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 clearly states context of use: omit postId to create, supply postId to schedule an existing draft, and notes the org approval flow that yields PENDING_APPROVAL. It stops short of naming alternatives or exclusions (e.g., how this differs from post_reschedule), leaving routing between write tools to inference.

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

Deploy Server

Other Tools