Skip to main content
Glama
adaptlypost

AdaptlyPost

Official
by adaptlypost
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Bulk Schedule Posts

bulk_schedule_posts

Schedule up to 100 posts in one call to shared platforms and accounts. Each is validated independently, so one failure won't block the rest.

Instructions

Schedule up to 100 posts in one call to the same platforms and accounts. Each item supplies its own text, contentType, scheduledAt, and optional media; platforms, connection-id arrays, timezone, and platform configs are shared by every item. Items are processed independently: each is validated and created like create_post, so one bad item fails alone while the rest are scheduled. Returns { totalScheduled, totalFailed, results[] } with a postId or errorMessage per item, in input order; read every row. An item with a past scheduledAt publishes immediately rather than being rejected. Call list_accounts first; TikTok needs tiktokConfigs with privacyLevel and Pinterest needs pinterestConfigs with boardId. Use create_post for a single post or a draft; this tool has no draft mode.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
postsYes1 to 100 posts to schedule; each is created independently
pageIdsNoFacebook page account ids from list_accounts (the account id; its pageId value is also accepted). Facebook has no connection-id array
timezoneNoIANA timezone stored with every post for display; does not shift scheduledAtUTC
platformsYesTarget platforms shared by every item. Each needs its connection-id array (pageIds for FACEBOOK)
tiktokConfigsNoTikTok per-connection config. Each entry needs connectionId + privacyLevel at minimum
youtubeConfigsNoYouTube per-connection config with video title, tags, privacy, etc.
facebookConfigsNoFacebook per-page config with post type and video title. pageId must match an entry in pageIds
instagramConfigsNoInstagram per-connection config to set post type (FEED, REEL, STORY)
pinterestConfigsNoPinterest per-connection config. Each entry needs connectionId + boardId; there is no API to list boards, so ask the user for the board id
tiktokConnectionIdsNoTikTok account connection IDs to post from
blueskyConnectionIdsNoBluesky account connection IDs to post from
threadsConnectionIdsNoThreads account connection IDs to post from
twitterConnectionIdsNoX (Twitter) account connection IDs to post from
youtubeConnectionIdsNoYouTube channel connection IDs to post from
linkedinConnectionIdsNoLinkedIn account connection IDs to post from
instagramConnectionIdsNoInstagram account connection IDs to post from
pinterestConnectionIdsNoPinterest account connection IDs to post from

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultNoAn object with totalScheduled, totalFailed, and results: one { postId, success, isScheduled, scheduledAt, errorMessage } per input item, in input order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.1.1
    • changedInput schema / properties / facebookConfigs / description
      Previous value: -"Facebook per-page config with post type and video title"New value: +"Facebook per-page config with post type and video title. pageId must match an entry in pageIds"
    • changedInput schema / properties / pageIds / description
      Previous value: -"Facebook page IDs"New value: +"Facebook page account ids from list_accounts (the account id; its pageId value is also accepted). Facebook has no connection-id array"
    • changedInput schema / properties / pinterestConfigs / description
      Previous value: -"Pinterest per-connection config. boardId is required for Pinterest posts"New value: +"Pinterest per-connection config. Each entry needs connectionId + boardId; there is no API to list boards, so ask the user for the board id"
    • changedInput schema / properties / platforms / description
      Previous value: -"Target platforms"New value: +"Target platforms shared by every item. Each needs its connection-id array (pageIds for FACEBOOK)"
    • changedInput schema / properties / posts / description
      Previous value: -"Array of posts to schedule"New value: +"1 to 100 posts to schedule; each is created independently"
    • addedInput schema / properties / posts / items / properties / contentType / description
      Added value: +"TEXT, IMAGE, VIDEO, or CAROUSEL; must match mediaUrls"
    • changedInput schema / properties / posts / items / properties / mediaUrls / description
      Previous value: -"Image or video URLs to attach"New value: +"publicUrl values from upload_media; unstored URLs fail this item"
    • addedInput schema / properties / posts / items / properties / platformTexts / description
      Added value: +"Per-platform caption overrides for this item"
    • changedInput schema / properties / posts / items / properties / scheduledAt / description
      Previous value: -"ISO 8601 schedule time"New value: +"Absolute ISO 8601 instant; a past time publishes immediately"
    • changedInput schema / properties / timezone / description
      Previous value: -"IANA timezone"New value: +"IANA timezone stored with every post for display; does not shift scheduledAt"
    • changedOutput schema / properties / result / description
      Previous value: -"The created scheduled post records with their ids, statuses, and schedule times as returned by the AdaptlyPost API."New value: +"An object with totalScheduled, totalFailed, and results: one { postId, success, isScheduled, scheduledAt, errorMessage } per input item, in input order."
  2. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnly=false and destructive=false. The description discloses independent item processing, partial failure isolation, immediate publishing for past scheduledAt, and the exact result structure with instruction to read every row. These are valuable behavioral details beyond annotations.

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 long but dense; it front-loads the core capability and then covers behavior, prerequisites, and alternatives. While it could be organized into bullets for easier scanning, every sentence contributes needed information without redundancy.

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?

Given the tool's complexity (17 parameters, multiple platforms, output schema), the description covers prerequisites, platform-specific requirements, partial failure behavior, return format, and how to interpret results. It leaves nothing critical for correct invocation unexplained.

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%, but the description adds meaning by distinguishing shared vs per-item parameters and highlighting required platform configs (tiktokConfigs, pinterestConfigs). It clarifies that each post item supplies its own text/contentType/scheduledAt/media while platforms and connection arrays are common.

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 states a specific verb and resource: 'Schedule up to 100 posts in one call to the same platforms and accounts.' It explicitly distinguishes from create_post by noting the bulk capability and the absence of a draft mode, making the tool's scope unambiguous.

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

Usage Guidelines5/5

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

It explicitly says to use create_post for a single post or draft, names list_accounts as a prerequisite, and gives platform-specific requirements (TikTok needs tiktokConfigs with privacyLevel, Pinterest needs pinterestConfigs with boardId). This clearly tells the agent when to choose this tool and what to prepare 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