このMCPでできること
Drafts, validates, schedules, publishes, and analyzes posts across connected social media accounts.
機能
ツール
17
ツール
create_post
Create a post
Create a social post on iHatePosting. action 'draft' saves it (the default, and the safe choice); 'schedule' needs scheduledDate (YYYY-MM-DD) + scheduledTime (e.g. '9:00 AM', in the account owner's timezone); 'now' publishes immediately to a real audience. Platforms with requirements — Pinterest a board, YouTube a title, TikTok and Instagram media — are set through `options` and `mediaIds`; call get_platform_rules for what each one needs, and validate_post to check before you commit. The reply lists every send it created, each naming its account (handle, displayName, nickname) AND carrying its own `postId` — tell the user what it says rather than what you asked for; they are not always the same. A multi-platform post is stored as one post per send, so that `postId` is what cancels or reschedules a single platform later without touching the others.
破壊的操作あり
外部アクセスあり
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['text', 'platforms'], 'properties': {'text': {'type': 'string', 'minLength': 1, 'description': 'The post text'}, 'action': {'enum': ['now', 'schedule', 'draft'], 'type': 'string', 'default': 'draft'}, 'options': {'type': 'object', 'description': "Per-platform options, e.g. { pinterest: { boardId: '...' }, youtube: { ytTitle: '...' } }", 'propertyNames': {'type': 'string'}, 'additionalProperties': {'type': 'object', 'propertyNames': {'type': 'string'}, 'additionalProperties': {}}}, 'mediaIds': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Media library ids from list_media or upload_media, in attach order'}, 'overrides': {'type': 'object', 'description': "Different text for one platform, e.g. { x: 'a shorter version' }", 'propertyNames': {'type': 'string'}, 'additionalProperties': {'type': 'string'}}, 'platforms': {'type': 'array', 'items': {'type': 'string', 'maxLength': 64, 'minLength': 1}, 'minItems': 1, 'description': 'Where it goes. Either a platform name — bluesky, x, linkedin, facebook, threads, mastodon, telegram, discord, tumblr, slack, instagram, pinterest, tiktok, youtube — which targets EVERY account you have on that platform, or an account id from list_accounts to target exactly one. Mix them freely.'}, 'scheduledDate': {'type': 'string', 'description': 'YYYY-MM-DD (schedule only)'}, 'scheduledTime': {'type': 'string', 'description': "e.g. '9:00 AM' (schedule only)"}}}
delete_post
Delete a post from iHatePosting
Delete a post from iHatePosting. ONE SEND AT A TIME: a post going to several accounts is stored as one post PER SEND, so deleting one cancels only that platform and leaves the rest scheduled — pass the `postId` that create_post returned on that particular send, or the id of the row list_posts shows for it. There is no need to cancel a whole multi-platform post to drop one platform from it. THIS DOES NOT UNPUBLISH ANYTHING: a post that has already gone out stays live on the network, and deleting it here only removes iHatePosting's record of it. For that reason a published post is refused unless you pass force: true, and you should only do that after telling the user in words that the platform post will remain. A post that is publishing at this moment is never deletable, forced or not — the worker is mid-flight on it. Deleting a scheduled post stops it going out.
破壊的操作あり
冪等
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['postId'], 'properties': {'force': {'type': 'boolean', 'description': 'Required to delete a post that already published. The platform post stays live — say so before using this.'}, 'postId': {'type': 'string', 'minLength': 1, 'description': 'Post id from list_posts'}}}
get_analytics
Get post analytics
How the posts actually performed: impressions, engagement and follower numbers per connected channel, plus the top posts. Use this to answer 'how did that do', 'which platform is working' or 'what should I post more of' — it reports what iHatePosting collected from each network, not an estimate. Some platforms report nothing (they are named in `unmeasuredPlatforms`), so a zero there means 'not measurable', not 'no reach'. If a plan ever gates a range, the answer says so in a sentence with `locked: true` rather than returning silently empty numbers.
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'range': {'enum': ['7d', '15d', '30d', '90d', '12m', 'all'], 'type': 'string', 'default': '30d', 'description': "How far back to look. '12m' is a year; 'all' is everything we have recorded."}}}
get_platform_rules
Get each platform's posting rules
What each platform will and will not accept: character limit, whether media is required, how many images, video formats and length, and which per-platform options are MANDATORY (e.g. Pinterest needs a board, YouTube needs a title). Call this BEFORE writing a post — it is the difference between composing something that publishes and something the platform rejects.
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
get_post
Get one post's details
Everything about ONE post: the shared text, each platform's own copy and options, the attached media, and per-send status with the live URL or the error. list_posts gives you the id; this explains what actually happened to it. Read it before update_post so you change what is there rather than overwriting it.
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['postId'], 'properties': {'postId': {'type': 'string', 'minLength': 1, 'description': 'Post id from list_posts'}}}
get_upload_ticket
Get a one-time upload ticket
Internal: issues a one-time ticket the upload box uses to send a file. The upload box calls this itself.
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
list_accounts
List connected social accounts
List the connected social accounts (platform, handle, health) available for posting. The response also names the iHatePosting account this connection acts for — if the accounts listed are not the ones you expect, check that `account.email` is the right person before assuming anything is missing.
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
list_media
List the media library
The images and videos already in the user's iHatePosting library, newest first, with the `id` that create_post's `mediaIds` wants. Call this whenever a platform needs a file — Instagram, Pinterest, TikTok and YouTube all do — to see whether what you need is already uploaded. Returns ids and dimensions only; there is no downloadable link, by design.
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'limit': {'type': 'integer', 'default': 20, 'maximum': 50, 'minimum': 1, 'description': 'How many of the newest assets to return'}}}
list_pinterest_boards
List Pinterest boards
The Pinterest boards you can pin to, with the `id` that create_post's `options.pinterest.boardId` requires. Pinterest REFUSES a pin without a board, and a board id is an opaque number you cannot guess — call this before creating any Pinterest post. If several Pinterest accounts are connected, pass `accountId` from list_accounts, because boards belong to one account and pinning to another account's board fails. An empty list with no error means the account is connected and simply has no boards yet — make one in Pinterest first.
読み取り専用
外部アクセスあり
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'accountId': {'type': 'string', 'maxLength': 64, 'minLength': 1, 'description': "Which Pinterest account's boards, from list_accounts. Omit to use the most recently connected one."}}}
list_posts
List recent posts
List posts with per-platform status (draft/scheduled/published/failed) and live URLs. Rows sharing a `batchId` are ONE submission the person made to several accounts — report them as one post going to N places, not as N posts. ALWAYS CHECK `total` IN THE REPLY: it is the number of posts matching your filter, and `returned` is how many you got. If they differ you are holding one page, not the answer — page on with `cursor` until `hasMore` is false before you count anything or tell anyone a number. Use `status` and `from`/`to` to ask the real question instead of counting a page: for "how many are scheduled" pass status 'scheduled' and read `total`; for a month or a date range pass from/to, which match the SCHEDULED time.
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'to': {'type': 'string', 'description': 'Latest SCHEDULED time, same formats. Inclusive of the whole day when given as a date.'}, 'from': {'type': 'string', 'description': "Earliest SCHEDULED time, 'YYYY-MM-DD' or an ISO timestamp. Inclusive, and a bare date means the whole day."}, 'limit': {'type': 'integer', 'maximum': 200, 'minimum': 1, 'description': 'Posts per page, default 50, max 200.'}, 'cursor': {'type': 'string', 'description': 'From `nextCursor` in the previous reply. Keep going while `hasMore` is true.'}, 'status': {'enum': ['draft', 'scheduled', 'publishing', 'published', 'partial', 'failed'], 'type': 'string', 'description': 'Only posts in this state. For a count, set this and read `total` — do not count the page.'}}}
open_upload_widget
Show an upload box
Show the person their iHatePosting media box: they can upload an image or video from their own device, browse what is already in their library with every file previewable, see how much storage their plan leaves them, pick a file to use, or delete one. THIS IS THE ANSWER WHENEVER SOMEONE NAMES A FILE ON THEIR OWN COMPUTER — a path like C:\clips\launch.mp4 or ~/Movies/clip.mov is not something any tool here can read, and explaining that is not an answer: open this instead, in the same reply, and they pick the file from a picker right in the conversation. Also use it for anything they pasted or attached here. Do NOT try to send those bytes yourself — they would travel as your own output and arrive cut short. If the file already has a public address, use upload_media with `url` instead.
読み取り専用
冪等
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
reschedule_post
Reschedule a post
Move a scheduled post to a different date and time. ONE SEND AT A TIME: a post going to several accounts is stored as one post per send, so this moves just that platform and leaves the others where they are. Takes the post id from list_posts, plus scheduledDate (YYYY-MM-DD) and scheduledTime (e.g. '9:00 AM') read in the ACCOUNT OWNER'S timezone, not yours or the user's device. A post that has already published cannot be moved — its time is a record of what happened — and one that is publishing right now is refused until it finishes.
破壊的操作あり
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['postId', 'scheduledDate', 'scheduledTime'], 'properties': {'postId': {'type': 'string', 'minLength': 1, 'description': 'Post id from list_posts'}, 'scheduledDate': {'type': 'string', 'pattern': '^\\d{4}-\\d{2}-\\d{2}$', 'description': 'YYYY-MM-DD'}, 'scheduledTime': {'type': 'string', 'maxLength': 20, 'minLength': 1, 'description': "e.g. '9:00 AM'"}}}
retry_post
Retry a failed post
Send a failed post again. ONE SEND AT A TIME, usually: a post to several accounts is stored as one post per send, so a post id normally names a single platform and retrying it touches only that one. (An older row, or a draft, can still carry several — without targetId every failed platform on that row is retried; with one, only that send.) Only a send that FAILED is retried — one that published is left alone, so this cannot double-post. If the cause was the account rather than the post (a revoked or paused connection) the answer says so, and retrying will not help until the user reconnects.
破壊的操作あり
外部アクセスあり
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['postId'], 'properties': {'postId': {'type': 'string', 'minLength': 1, 'description': 'Post id from list_posts'}, 'targetId': {'type': 'string', 'description': "Retry ONE platform's send, if you already hold that send's id. Omit it to retry every failed send on the post."}}}
update_post
Replace a draft or scheduled post
Rewrite a draft or scheduled post. THIS REPLACES THE WHOLE POST, so read it with get_post first and send back the complete set — anything you leave out is removed, including platforms and per-platform options. Note the shape differs from create_post: this one wants `accountIds` (the ids from list_accounts, NOT platform names) and it requires `action`. Two limits: a post that has already published cannot be rewritten at all, and a post that goes to several platforms and was saved as a group keeps the platforms it has — send back that row's own accountIds and everything else is editable, but adding or swapping an account is refused with a sentence saying so, because it would publish some platforms twice. To change which platforms a group posts to, delete it and create it again.
破壊的操作あり
外部アクセスあり
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['postId', 'baseContent', 'accountIds', 'action'], 'properties': {'action': {'enum': ['draft', 'schedule', 'now'], 'type': 'string', 'description': "'draft' keeps it unscheduled, 'schedule' needs the date and time below, 'now' publishes to a real audience."}, 'postId': {'type': 'string', 'minLength': 1, 'description': 'Post id from list_posts'}, 'options': {'type': 'object', 'description': "Per-platform options, e.g. { pinterest: { boardId: '...' } }", 'propertyNames': {'type': 'string'}, 'additionalProperties': {'type': 'object', 'propertyNames': {'type': 'string'}, 'additionalProperties': {}}}, 'mediaIds': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Ids from list_media or upload_media, in attach order'}, 'overrides': {'type': 'object', 'description': 'Different text for one platform', 'propertyNames': {'type': 'string'}, 'additionalProperties': {'type': 'string'}}, 'accountIds': {'type': 'array', 'items': {'type': 'string'}, 'minItems': 1, 'description': 'The FULL set of destination account ids, from list_accounts. Account IDS, not platform names. Anything omitted is removed from the post.'}, 'baseContent': {'type': 'string', 'minLength': 1, 'description': 'The shared text. REQUIRED — it replaces what is there.'}, 'scheduledDate': {'type': 'string', 'pattern': '^\\d{4}-\\d{2}-\\d{2}$', 'description': 'YYYY-MM-DD (schedule only)'}, 'scheduledTime': {'type': 'string', 'maxLength': 20, 'description': "e.g. '9:00 AM', in the account owner's timezone (schedule only)"}}}
upload_media
Upload media to the library
Put an image or video into the library and get back an id for create_post. PREFER `url` — ALWAYS, including for a picture you just generated: we fetch it ourselves at full length, and it is the only thing that works for video or for anything more than a few kilobytes. We take whatever the link serves, so a CDN that will not name the type (application/octet-stream, as presigned S3, Drive and Dropbox links do) is fine. `base64` is a last resort for small files that exist at no address: it travels as your own output, a conversation truncates it, and the cut-off file is refused. Either way the API checks type, size and quota, then registers the file.
外部アクセスあり
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {'url': {'type': 'string', 'maxLength': 2048, 'minLength': 1, 'description': "Public https link to the file ITSELF, not to a page showing it. We download it. Use this whenever the file has an address. A path on the person's own computer is NOT a link — nothing here can read their disk; call open_upload_widget instead."}, 'mime': {'type': 'string', 'minLength': 1, 'description': "e.g. 'image/jpeg', 'image/png', 'video/mp4'. Required with `base64`; with `url` the server's own content type decides."}, 'base64': {'type': 'string', 'minLength': 1, 'description': "The file's bytes, base64. A data: prefix is stripped. LAST RESORT, and small files only. Everything here becomes YOUR OWN OUTPUT, and a long string of it gets cut short on the way — the file then arrives incomplete and we refuse it. AN IMAGE YOU JUST GENERATED IS NOT AN EXCEPTION: it is the most common thing to fail this way, and it almost always has a URL of its own, so pass that as `url` instead and we fetch it at full length. Use base64 only for something genuinely small that exists at no address at all. If a file was pasted or attached to this conversation, never send it here — call open_upload_widget, or, if you can run shell commands, `ihateposting upload <path>`."}, 'altText': {'type': 'string', 'maxLength': 1000, 'description': 'Alt text. Worth writing — several networks publish it.'}, 'filename': {'type': 'string', 'maxLength': 200, 'minLength': 1, 'description': "e.g. 'launch-photo.jpg' — the library label. Optional with `url`, where the link's own name is used."}}}
validate_post
Check a post before sending
Check a post against every platform you plan to send it to, WITHOUT creating anything. Runs the same checks create_post runs, so the answer is what will really happen: platform rules ('X counts this as 1200/280 characters', 'YouTube needs a title', 'TikTok slideshows take JPEG or WebP photos'), whether each account is connected and signed in, AND the account's own limits — trial expiry, whether the plan includes X, and the monthly posting allowances. Pass the same `action`/`scheduledDate`/`scheduledTime` you will pass to create_post: a cap counts the month the post is DUE, so checking without them answers a different question. Anything not tied to one platform comes back under the key "account". Free to call as often as you like; use it before create_post rather than discovering a problem after the post is spent.
読み取り専用
外部アクセスあり
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'required': ['text'], 'properties': {'text': {'type': 'string', 'description': 'The post text'}, 'action': {'enum': ['now', 'schedule', 'draft'], 'type': 'string', 'description': "What you will ask create_post for. Defaults to 'now' — the strictest check. 'draft' skips the limits, because a draft costs nothing."}, 'targets': {'type': 'array', 'items': {'type': 'object', 'required': ['platform'], 'properties': {'options': {'type': 'object', 'description': 'Per-platform options — see get_platform_rules', 'propertyNames': {'type': 'string'}, 'additionalProperties': {}}, 'platform': {'enum': ['bluesky', 'x', 'linkedin', 'facebook', 'threads', 'mastodon', 'telegram', 'discord', 'tumblr', 'slack', 'instagram', 'pinterest', 'tiktok', 'youtube'], 'type': 'string'}, 'contentOverride': {'type': 'string', 'description': 'Different words for this platform'}}}, 'minItems': 1, 'description': 'Platforms with their per-platform options. Use this OR `platforms`.'}, 'mediaIds': {'type': 'array', 'items': {'type': 'string'}, 'description': 'Media library ids from list_media or upload_media, in attach order'}, 'platforms': {'type': 'array', 'items': {'enum': ['bluesky', 'x', 'linkedin', 'facebook', 'threads', 'mastodon', 'telegram', 'discord', 'tumblr', 'slack', 'instagram', 'pinterest', 'tiktok', 'youtube'], 'type': 'string'}, 'minItems': 1, 'description': 'Shorthand for targets. PLATFORM NAMES ONLY — an account id belongs in create_post, not here. Use this OR `targets`.'}, 'scheduledDate': {'type': 'string', 'description': "YYYY-MM-DD, with action 'schedule'. The monthly limits count the month the post is DUE, so this changes the answer."}, 'scheduledTime': {'type': 'string', 'description': "e.g. '9:00 AM' (with action 'schedule'), in the account owner's timezone"}}}
whoami
Show the signed-in iHatePosting account
Which iHatePosting login this connection acts for (email and account name), whether it connected by signing in or with an API key. Use this for any question about who the user is or which account is connected. This is NOT a social media handle — the handles from list_accounts belong to the connected profiles, which may carry other people's names.
読み取り専用
入力スキーマ
{'type': 'object', '$schema': 'http://json-schema.org/draft-07/schema#', 'properties': {}}
履歴
最近のツール変更
変更
delete_post
2026年9月29日3:02
変更
retry_post
2026年9月29日3:02
変更
upload_media
2026年9月29日3:02
変更
reschedule_post
2026年9月29日3:02
変更
list_accounts
2026年9月29日3:02
変更
list_posts
2026年9月29日3:02
変更
create_post
2026年9月29日3:02
変更
validate_post
2026年9月29日3:02
変更
whoami
2026年9月29日3:02
追加
get_upload_ticket
2026年9月29日3:02
追加
open_upload_widget
2026年9月29日3:02
変更
delete_post
2026年9月25日3:02
変更
retry_post
2026年9月25日3:02
変更
update_post
2026年9月25日3:02
変更
get_post
2026年9月25日3:02
変更
upload_media
2026年9月25日3:02
変更
list_media
2026年9月25日3:02
変更
reschedule_post
2026年9月25日3:02
変更
get_analytics
2026年9月25日3:02
変更
list_pinterest_boards
2026年9月25日3:02
変更
list_accounts
2026年9月25日3:02
変更
list_posts
2026年9月25日3:02
変更
create_post
2026年9月25日3:02
変更
validate_post
2026年9月25日3:02
変更
get_platform_rules
2026年9月25日3:02
変更
whoami
2026年9月25日3:02
追加
list_pinterest_boards
2026年9月19日2:51
追加
delete_post
2026年9月17日12:35
追加
retry_post
2026年9月17日12:35
追加
update_post
2026年9月17日12:35
関連MCP
類似のMCPサーバー
captapi
io.github.CDCStream/captapi
Retrieves social media profiles, posts, engagement metrics, comments, marketplace listings, events, and Meta advertising data acr…
SendIt
io.github.Shree-git/sendit
Plans, generates, approves, schedules, publishes, and analyzes social media content across LinkedIn, Instagram, Threads, TikTok, …
aidelly
io.github.wilzer/aidelly
Supports agency social media operations including content creation, approvals, scheduling, publishing, repurposing, analytics, ec…
LinkedIn MCP Server (Salesbot)
cz.salesbot/linkedin-mcp-server
Supports LinkedIn lead discovery, contact enrichment, CRM pipelines, campaign sequencing, message approval and human-reviewed out…
excalibur-mcp
io.github.lonniev/excalibur-mcp
Creates, schedules, manages, and measures formatted posts for X, with OAuth, snippets, writing voice, and post performance tracki…
uplika
com.uplika/uplika
Publishes and manages posts, replies, messages, media, and automations across connected social platforms.
Prowlo — Reddit & X for AI agents
com.prowlo/reddit-x
Indexes and searches Reddit and X-related social data, discovers communities, monitors keywords, finds engagement opportunities, …
ChiefLab
io.github.bdentech/chieflab
Runs approval-gated product launch workflows with channel-specific marketing drafts, social publishing, email actions, measuremen…