Skip to main content
Glama
dinwal

RecurPost MCP Server

by dinwal
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

post_content

Post content immediately or schedule it for a future time on a social account. Provide the account ID, message, and optional media to publish or queue the post.

Instructions

Post content immediately or schedule it for a future time on a social account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesSocial account ID (from social_account_list)
urlNoWebsite link to include
gbp_ctaNoGoogle Business Profile call to action
messageYesPost content text
pi_titleNoPinterest pin title
yt_thumbNoYouTube custom thumbnail URL
yt_titleNoYouTube video title
image_urlNoArray of image URLs to attach
video_urlNoPublic video URL to attach
bs_messageNoBluesky-specific message override
fb_messageNoFacebook-specific message override
in_messageNoInstagram-specific message override
ln_messageNoLinkedIn-specific message override
pi_messageNoPinterest-specific message override
th_messageNoThreads-specific message override
tk_messageNoTikTok-specific message override
tw_messageNoTwitter/X-specific message override
yt_messageNoYouTube-specific message override
gbp_cta_urlNoGoogle Business Profile CTA URL
gmb_messageNoGoogle Business Profile-specific message override
ln_documentNoLinkedIn document URL (PPT/PDF/DOCX)
yt_categoryNoYouTube video category
fb_post_typeNoFacebook post type
in_post_typeNoInstagram post type
workspace_idNoWorkspace ID (ws_id from workspace_list). Omit to use your default workspace.
yt_user_tagsNoYouTube tags
first_commentNoDefault first comment
tk_allow_duetNoAllow TikTok duets
fb_first_commentNoFacebook first comment
in_first_commentNoInstagram first comment
ln_first_commentNoLinkedIn first comment
ln_document_titleNoLinkedIn document title
tk_allow_commentsNoAllow TikTok comments
tk_allow_stitchesNoAllow TikTok stitches
tk_privacy_statusNoTikTok privacy status
yt_privacy_statusNoYouTube privacy status
schedule_date_timeNoSchedule time in YYYY-MM-DD HH:MM:SS format. Omit for immediate posting.
in_reel_share_in_feedNoShare Instagram reel in feed
yt_video_made_for_kidsNoIs the YouTube video made for kids
host_images_on_recurpostNoHost images on RecurPost (default: true)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.3
    • addedInput schema / properties / workspace_id
      Added value: +{
+  "description": "Workspace ID (ws_id from workspace_list). Omit to use your default workspace.",
+  "type": "string"
+}
  2. First observedv1.0.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full burden. It only states that content is posted immediately or scheduled, but does not disclose irreversibility, failure modes, rate limits, or authentication requirements. For a mutation tool, this is a significant gap.

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?

The description is a single, front-loaded sentence with zero waste. It is concise, but given the tool's complexity, it is arguably too sparse; however, the structure itself is efficient.

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?

With 40 parameters, no output schema, and no annotations, the description is severely under-specified. It fails to explain platform-specific overrides, scheduling format, workspace handling, or any operational nuance, making it inadequate for an agent to use correctly.

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 fully documents all 40 parameters. The description adds no additional parameter meaning beyond what the schema provides, warranting the baseline score of 3.

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 verb 'post' and the resource 'content on a social account', and distinguishes it from siblings like generate_content_with_ai (generation) and social_account_list (listing). The action is unambiguous.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool vs. alternatives. It does not mention exclusions, prerequisites (like having a connected account), or when not to use it, leaving the agent to infer from context.

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