Skip to content

Developers

Social media MCP tool catalogue

SkedCast's social media MCP tools, all 59 of them — 31 that only read and 28 that change something — with its scope and description, read straight from the server’s own tool registry.

Read tools (31)

ToolDescriptionScope
list_scheduled_postsList the workspace's posts (queue, drafts, published) newest-first, with optional status / client / platform filters and free-text search (`q`) over captions, per-platform overrides, client names and account handles.posts.read
list_post_targetsList individual post DESTINATIONS (one row per platform account) with optional status / client / account / platform / free-text filters and a SCHEDULE-time window — the tool for "what publishes on this date". Carries `total` and `totalPosts`, so a caller can tell a full page from a complete set.posts.read
get_postGet one post with its per-platform variants and fan-out targets.posts.read
list_clientsList the workspace's client groups (brands / influencers).clients.read
list_accountsList connected social accounts, optionally filtered by client or platform.accounts.read
get_analytics_overviewReach / impressions / engagement plus a per-platform rollup over a date window.analytics.read
get_post_analyticsPer-post performance (complements get_analytics_overview): one post’s lifetime per-target breakdown by postId, or a keyset page of per-post rows with filters.analytics.read
get_account_analyticsOne channel’s totals and daily series, plus the two things no other tool carries: profile-level activity (profile views, link taps, video plays) and follower demographics.analytics.read
list_library_assetsList content-library (DAM) assets with optional kind / folder / label / client / status / search filters. Filter `status: "transcoded"` for assets that are actually publishable; every row also carries `status`, `publishable` and `ready`.media.read
get_capabilitiesThe per-platform composing rulebook: caption and hashtag limits, media rules per kind (counts, formats, file-size ceiling, duration bounds, aspect ratios), post types, native-scheduling window, default cadence, first-comment support, and the `variants[].overrides` keys each platform requires or accepts. Read it before composing instead of discovering a limit by failing a publish.posts.read
get_agencyThe current workspace profile — name, plan, app mode, settings, and the caller’s role.agency.read
list_reportsList the workspace's saved analytics report definitions.reports.read
get_best_timesWorker-derived best posting times (strongest-first), optionally by client / platform.besttimes.read
list_approvalsList the workspace's approval queue (pending and decided requests), newest-first, with optional status / post filters.approvals.read
get_posting_limitsAnti-ban posting limits (cadence): one account by socialAccountId, or every active channel plus the tenant bypass flag when omitted.accounts.read
get_quotaAdaptive quota pool: your scarce-bucket budget (guaranteed slice, used, burst headroom, tomorrow’s guarantee tonight, reset clock) — read before planning a batch.accounts.read
list_campaignsList the workspace's campaigns (named post groupings), optionally filtered by client / status.campaigns.read
validate_postDry-run a compose request and get the per-platform verdict WITHOUT writing anything — same arguments as create_post, no post row and no draft. Returns `{ valid, platforms[], estimatedCostUsd }`. Does not run cadence or quota admission, so `valid: true` means the shape is acceptable, not that a publish cannot later be deferred.posts.compose
list_webhooksList the workspace's outbound webhook endpoints (url, subscribed events, active flag; secret masked).webhooks.read
get_webhookRead one webhook endpoint — URL, subscribed events, active state, consecutive failures, and when/why it was auto-disabled. The signing secret is never returned here.webhooks.read
list_webhook_deliveriesThe delivery log for one endpoint — each attempt with its event type, response status, error and timing. How you find out WHY an endpoint stopped receiving.webhooks.read
get_campaignRead one campaign in full — name, description, status, colour, date range, owning client and post counts.campaigns.read
get_clientRead one client group in full — name, type, approval policy, posting rules, brand voice and default timezone.clients.read
get_post_targetRead a single fan-out destination in full — status, scheduled time, platform, account, published permalink and external id, and its failure reason when it failed.posts.read
get_post_recycleRead one post’s evergreen re-posting configuration and the worker’s bookkeeping. Returns null when the post is not enrolled.posts.read
get_accountRead one connected social account in full — platform, handle, display name, avatar, status (including whether it needs re-authorisation) and owning client.accounts.read
get_approvalRead one approval request with the gated post’s preview and roll-up, so a reviewer can see what they are deciding on before calling decide_approval.approvals.read
get_media_assetRead one content-library asset in full — filename, kind, size, dimensions, duration, folder, labels, alt text, pipeline status, and the publishable/ready flags plus the per-platform readiness map.media.read
get_client_analyticsOne client group’s analytics — totals, a per-platform breakdown and a time series. A different projection from get_analytics_overview filtered by client.analytics.read
get_reportRead one report definition with its run history — each run’s status, window, and whether an export is available.reports.read
download_report_exportGet a time-limited download URL for one completed report run’s export file. The URL expires — fetch it when you are ready to use it.reports.read

Write tools (28)

ToolDescriptionScope
decide_approvalApprove, reject, or request changes on a pending approval request (approve releases the gated post for publishing). A write action — confirm with the user before calling.approvals.decide
revise_postChange the CONTENT of an already-scheduled post — caption, media, cover, alt text, per-platform overrides — without disturbing its destinations. Send only what you are changing. Refuses, naming them, when a destination has already published or is about to. An edit to an APPROVED post returns it to review. A write action — confirm with the user before calling.posts.compose
create_postCompose a post and fan it out across the selected accounts (or save it as a draft). Retry-safe: retrying with identical arguments replays the original result instead of creating a duplicate. Note: two publish-now calls with byte-identical content and targets are treated as the same post and coalesced permanently — to intentionally publish the same content twice, vary the content or use distinct scheduled times. For platform-specific settings (e.g. YouTube privacy, TikTok privacy level, Pinterest board, Telegram chat), set `variants[].overrides`. That same object carries `firstComment`: a reply posted automatically once the destination goes live, so a "link in the comments" post needs no manual follow-up. Supported on X, LinkedIn, YouTube, Instagram, Facebook, Threads, Telegram and Bluesky (not TikTok or Pinterest); spell it exactly `firstComment`. Overrides are free-form — an unrecognised key is accepted and silently ignored — and the comment is best-effort: if it fails the post still publishes and nothing is reported, so confirm on the published post. A write action — confirm with the user before calling.posts.compose
create_posts_bulkCreate up to 50 posts in one call. Each item is exactly the arguments of create_post, so a bulk item carries every override a single post does (per-platform caption, title, cover, per-asset alt text, first comment, per-platform settings). Items are created one after another, each on its own: one failing never rolls back the others, and the result lists every item in order with its post id or its error. Retry-safe: retrying with identical arguments creates nothing twice. Pass validateOnly:true to check every item without writing anything. It counts one request-budget unit per item. This creates real outbound content — confirm with the user before calling. Requires the posts.compose scope.posts.compose
update_postReplace a draft post in place — its content, media, targets, and schedule. Only draft posts can be updated. Platform-specific settings live in `variants[].overrides`, same as create_post, including `firstComment`. A write action — confirm with the user before calling.posts.compose
import_mediaIngest an external image / video into the content library by URL — the file must already be reachable at a public URL. For bytes you already hold (an image you just rendered, or a local file) use `upload_media` instead. A write action — confirm with the user before calling.media.manage
upload_mediaUpload a LOCAL image / video into the content library and get back a media id for create_post. Sends the file inline (≤18 MiB) or returns a presigned URL for larger files. A write action — confirm with the user before calling.media.manage
reschedule_postMove a pending post target to a new time (absolute scheduledAt or relative shiftMinutes). A write action — confirm with the user before calling.posts.compose
bulk_post_target_actiondestructiveReschedule, retry or cancel up to 5000 post targets in one call — the batch form of reschedule_post / retry_post / cancel_post. Returns `{ jobId, accepted, skipped, skippedReasons? }`; a skipped target is reported, never silently dropped. A write action — confirm with the user before calling.posts.compose
cancel_postdestructiveCancel a still-pending post target before it publishes. A write action — confirm with the user before calling.posts.compose
retry_postRe-queue a failed or rate-limited post target so it publishes again. A write action — confirm with the user before calling.posts.compose
set_post_recycleSet, update, or disable a post's evergreen recycle settings (interval / times / end date / max recycles). A write action — confirm with the user before calling.posts.compose
shift_campaignMove a whole campaign's pending schedule by a relative number of minutes. A write action — confirm with the user before calling.campaigns.manage
create_webhookRegister an outbound webhook endpoint for HMAC-signed event deliveries. Subscribe to any subset of the full 40-event catalog — see /developers/webhooks, or the `webhooks` block in openapi.json, for the complete list with payload fields. Returns the signing secret once. A write action — confirm with the user before calling.webhooks.manage
delete_webhookdestructiveDelete an outbound webhook endpoint by id (deliveries cascade). A write action — confirm with the user before calling.webhooks.delete
create_clientCreate a new client group (a brand or influencer whose accounts are managed together). A write action — confirm with the user before calling.clients.manage
create_connect_inviteMint a shareable self-connect link so a client can connect the requested platforms themselves; returns the link and its expiry. A write action — confirm with the user before calling.accounts.connect
update_webhookChange an endpoint’s URL, event list, or active state — including re-enabling one auto-disabled after repeated failures. The event list REPLACES the previous one. A write action — confirm with the user before calling.webhooks.manage
test_webhookSend a `webhook.test` delivery and report the outcome, proving an endpoint is reachable and verifying signatures without waiting for a real event. Performs a real outbound request — confirm with the user before calling.webhooks.manage
rotate_webhook_secretMint a new signing secret and return it ONCE — it is not readable again. The previous secret keeps verifying for a short overlap so the customer can redeploy without dropping deliveries. A write action — confirm with the user before calling.webhooks.manage
create_campaignCreate a campaign — a named group of posts with an optional client, colour and date range. Posts are added with assign_to_campaign. A write action — confirm with the user before calling.campaigns.manage
update_campaignChange a campaign’s name, description, status, colour or date range. A write action — confirm with the user before calling.campaigns.manage
delete_campaigndestructiveDelete a campaign. The posts in it are NOT deleted — they lose the grouping and keep their own schedules. A write action — confirm with the user before calling.campaigns.manage
assign_to_campaignAdd up to 500 existing posts to a campaign. Grouping only — no post’s content or schedule changes. A write action — confirm with the user before calling.campaigns.manage
unassign_from_campaignRemove posts from a campaign. Grouping only — the posts and their schedules are untouched. A write action — confirm with the user before calling.campaigns.manage
update_clientChange a client’s name, type, approval policy, posting rules, brand voice or default timezone. A write action — confirm with the user before calling.clients.manage
delete_clientdestructiveArchive a client group. OWNER ONLY — a Manager holding the clients.manage scope cannot do this. A write action — confirm with the user before calling.clients.manage
clear_post_recycleTurn OFF evergreen re-posting for a post. Idempotent. Already-scheduled recycled copies are not retracted — cancel those separately. A write action — confirm with the user before calling.posts.compose

Social media MCP tools: FAQ

Is this the complete, real list of SkedCast’s MCP tools?
Yes — every row is read directly from the same tool registry (59 tools) the remote MCP server itself exposes and the public developer docs render, so this page cannot list a tool the server doesn’t actually have, or miss one it does.
What does "write" mean for a tool?
A write tool changes something — creates, updates, reschedules, cancels. A compatible MCP host is expected to ask you to confirm before calling one, unlike a read tool, which runs freely within your granted scopes.
What does "destructive" mean?
A small subset of write tools (delete and cancel actions, plus the bulk action that can cancel or delete many targets in one call) draw on a tighter rate budget than an ordinary write, since undoing thousands of rows at once is a different risk than scheduling one post.
Can an agent call a tool outside my role’s permissions?
No — every tool call is checked against the scope of the member who connected the client; a tool listed here still can’t exceed what that person is allowed to do in the console.
How do I actually connect a client to call these tools?
Point a compatible MCP client at SkedCast's real remote server URL (https://api.skedcast.com/mcp) and sign in over OAuth 2.1 — see the MCP config generator for the exact connection details per client.

Ready to broadcast everywhere?

Sign up free — no credit card. You land on the Free plan, and you can start a one-time 7-day Studio trial from your workspace whenever you are ready. Connect your first accounts, import a batch, and watch one post fan out across every platform.