Loading ToolBench
AdaptlyPost MCP Server — AI agent integration for social media scheduling, posting, and analytics
AdaptlyPost MCP server provides 13 well-defined tools for social media management with mostly complete schemas and descriptions. All tools have clear verb-prefixed names (list_, create_, update_, delete_, get_, publish_, retry_, bulk_, upload_, etc.) that follow action-oriented naming conventions. Descriptions are present for all tools and range from moderate (50-80 chars) to detailed (150+ chars). Input parameters include type definitions and descriptions across most tools. However, several schemas lack complete documentation of return types/output schemas, and some complex parameter relationships (e.g., platform-specific config objects) are under-documented. Error handling and recovery guidance are minimal. The server demonstrates production intent with OAuth support, media handling, and proper secret injection via environment variables (ADAPTLYPOST_API_TOKEN in env, not params).
Create multiple posts in a single request
Create a social media post across one or more platforms
Delete a post (move to trash)
Get social media analytics for a date range and optional platforms
Get details of a specific post by ID
Get publishing results and platform-specific data for a post
Get signed upload URLs for media files
Output schemas not documented. Tools return complex results (post objects, analytics data, results arrays) but no response schema is visible in tool definitions. LLMs cannot plan downstream calls or extract nested fields without documented return structures.
Platform-specific config objects (TikTokConfigSchema, YouTubeConfigSchema, InstagramConfigSchema, FacebookConfigSchema, PinterestConfigSchema) defined in source but their parameter relationships and constraints are under-documented in tool descriptions. create_post accepts these configs but LLMs cannot understand when each is required or optional.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 69 | 2025-06-18+ | v2 |
List all connected social media accounts
List posts with optional filtering by status or platform
Publish a draft post immediately or reschedule it
Retry publishing a post to specific failed platforms
Update an existing post's text, schedule, or status
Download media from a URL and upload it to AdaptlyPost storage
Error handling and recovery guidance absent. Tools lack descriptions of failure modes (e.g., 'platform auth failed', 'media processing timeout', 'scheduling conflict') and what LLM should do next. No pattern for categorizing retryable vs. fatal errors.
No documented pagination limits or result caps. list_posts, list_accounts, and get_analytics accept limit/offset but maximum allowed values and default behavior are not stated. Without caps, LLMs may request excessive data, exhausting context windows.
Tool descriptions lack 'when to use this' context. E.g., get_post vs get_post_results, when should LLM call each? What's the difference? Why not combine them? Ambiguity forces the LLM to reason about intent.
Timezone parameter documentation incomplete. Multiple tools accept 'timezone' (scheduledAt, publish_post) but do not specify valid timezone format (IANA, UTC offset, etc.) or explain what happens if omitted. LLMs may pass invalid values.
connectionIds and pageIds parameter semantics unclear. Tools require connectionId for each platform but don't document whether multiple IDs must belong to the same user or can be mixed across accounts. LLMs may create confusing cross-account posts.