Skip to main content
Glama
FirstReply MCP Server

FirstReply MCP Server

Official
by FirstReply

Post Create

post_create

Save a social media post as a draft without publishing it, then schedule it later with post_schedule or in FirstReply.

Instructions

Save a social media post as a draft. Nothing is published: schedule it with post_schedule or in FirstReply.

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>",
      "content": "<content>"
    },
    "name": "post_create"
  }
}

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.
contentYesThe text of the 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).
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.3.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare the generic write profile (not read-only, not destructive, not idempotent), so the added value is the explicit statement that the record lands in draft state and is not published. That is meaningful behavioral context beyond annotations, though non-idempotency (duplicate drafts) and permission requirements are left unstated.

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?

Two short sentences, the draft semantics front-loaded and the follow-up action second. No filler, nothing repeated from structured fields.

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 a six-parameter create tool with nested per-channel settings and no output schema, the description covers the essential behavioral fact (draft, unpublished) while the schema handles the rest. It could say a bit more about what is returned (e.g. the draft id) and about the two channel-targeting styles, but nothing critical is missing.

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 description coverage is 100%, including detailed per-channel settings for targets, channelIds, media and organizationId, so the schema already carries parameter meaning. The description adds no parameter-level guidance of its own, which matches the baseline for fully documented schemas.

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 ('Save a social media post as a draft') and immediately contrasts the outcome with creation-via-scheduling, so an agent can tell it apart from post_schedule and post_write without reading any schema.

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?

Explicitly says nothing is published here and routes scheduling intent to post_schedule (or FirstReply), which is a real when-to-use boundary. It does not discuss the alternative of publishing immediately (post_write), so the routing guidance is clear but not exhaustive.

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