Skip to main content
Glama
peturgeorgievv-factory

postfast-mcp

by peturgeorgievv-factory
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

create_posts

Create and schedule social media posts in batches of up to 15, targeting specific social accounts with platform-specific controls.

Instructions

Create and schedule social media posts. Supports batch creation (up to 15 posts). Each post targets a specific social account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
postsYesArray of posts to create
statusNoPost status. SCHEDULED requires scheduledAt on all posts.SCHEDULED
approvalStatusNoApproval workflow statusAPPROVED
controlsYesPlatform-specific controls (shared across all posts in the batch)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed14 schema fields changedv0.1.9
    • addedInput schema / properties / controls / properties / gbpCallToActionType
      Added value: +{
+  "enum": [
+    "BOOK",
+    "ORDER",
+    "LEARN_MORE",
+    "SIGN_UP",
+    "CALL",
+    "SHOP"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / controls / properties / gbpCallToActionUrl
      Added value: +{
+  "description": "CTA button URL (not needed for CALL, ignored for OFFER)",
+  "type": "string"
+}
    • addedInput schema / properties / controls / properties / gbpEventEndDate
      Added value: +{
+  "description": "End date for EVENT/OFFER (ISO 8601)",
+  "type": "string"
+}
    • addedInput schema / properties / controls / properties / gbpEventStartDate
      Added value: +{
+  "description": "Start date for EVENT/OFFER (ISO 8601)",
+  "type": "string"
+}
    • addedInput schema / properties / controls / properties / gbpEventTitle
      Added value: +{
+  "description": "Title for EVENT/OFFER posts (max 58 chars)",
+  "type": "string"
+}
    • addedInput schema / properties / controls / properties / gbpLocationId
      Added value: +{
+  "description": "GBP location resource name (from list_gbp_locations)",
+  "type": "string"
+}
    • addedInput schema / properties / controls / properties / gbpOfferCouponCode
      Added value: +{
+  "description": "Coupon code (OFFER only)",
+  "type": "string"
+}
    • addedInput schema / properties / controls / properties / gbpOfferRedeemUrl
      Added value: +{
+  "description": "Redemption URL (OFFER only)",
+  "type": "string"
+}
    • addedInput schema / properties / controls / properties / gbpOfferTerms
      Added value: +{
+  "description": "Terms and conditions (OFFER only)",
+  "type": "string"
+}
    • addedInput schema / properties / controls / properties / gbpTopicType
      Added value: +{
+  "description": "Post type",
+  "enum": [
+    "STANDARD",
+    "EVENT",
+    "OFFER"
+  ],
+  "type": "string"
+}
    • removedInput schema / properties / controls / properties / xCommunityId
      Removed value: -{
-  "type": "string"
-}
    • removedInput schema / properties / controls / properties / xQuoteTweetUrl
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / posts / items / properties / mediaItems / items / properties / coverImageKey
      Added value: +{
+  "description": "S3 key of a custom cover/thumbnail image for video posts (upload via get_upload_urls first). Supported on Instagram Reels, Facebook Reels, Pinterest video pins.",
+  "type": "string"
+}
    • changedInput schema / properties / posts / items / properties / mediaItems / items / properties / coverTimestamp / description
      Previous value: -"Video cover timestamp"New value: +"Video cover timestamp in milliseconds (e.g. \"5000\" = 5s). Fallback when coverImageKey is also provided."
  2. First observedv0.1.0

TDQS

B3.4/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavior. It only says 'create and schedule' but omits side effects, permission requirements, rate limits, or what happens on failure. The mutation nature is implied but not detailed.

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 sentences, no redundancy, front-loaded with key information. Every word earns its place.

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

Completeness2/5

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

Given the tool's complexity (many nested controls, no output schema), the description is insufficient. It fails to explain workflow dependencies (e.g., media upload via get_upload_urls), the role of status/approval, or the return value. Much needed context 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%, so the schema documents all parameters. The description adds no meaningful value beyond the schema; it restates batch limits already present. Thus baseline 3 is appropriate.

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?

The description clearly states the tool creates and schedules social media posts, specifies batch support (up to 15), and notes each post targets a specific account. It effectively distinguishes from listing and deletion siblings.

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?

The description implies usage for creating posts but does not explicitly state when to use versus alternatives, nor provides exclusionary hints. No guidance on prerequisites like needing to upload media first.

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