MCP

Returns the signed-in account and the organizations it belongs to: email, name, timezone, the current time in that timezone, and for each organization its ID, name, plan limits and member count.

If you belong to more than one organization, an assistant will name them and ask which one you mean before going further.

Takes no parameters.

Example prompt: "Which Buffer organizations do I have access to?"

Lists the social accounts connected to an organization, with each channel's ID, name, display name, service, type, avatar and connection status.

Example prompt: "List all my connected Buffer channels."

Returns the detail that list_channels leaves out for a single channel: its posting schedule, posting goals, queue status, timezone, link shortening settings, and service-specific data such as Pinterest boards, a Mastodon server URL or Instagram reminder settings.

Example prompt: "What times does my LinkedIn channel post at?"

Lists posts in an organization. Returns each post's ID, status, text, scheduled and sent times, channel, tags, assets, via and any publishing error.

Each post also carries allowedActions, the list of what you can do with it, so an assistant can move straight to an edit or a delete without reading the post again to find out whether it is allowed.

Example prompt: "Show me all my draft posts in Buffer so I can review what's pending."

Reads one post in full: status, content, author, channel, tags, notes, assets and allowedActions, the list of what you are allowed to do with it. The metadata field carries service-specific data such as Instagram geolocation, a Twitter thread or YouTube privacy settings. A post with the error status carries the failure message.

Example prompt: "Why did my Instagram post from yesterday fail?"

Schedules or publishes a post on one channel. Works for Instagram, Facebook, Twitter, LinkedIn, Pinterest, YouTube, Google Business, Mastodon, TikTok, Threads, Bluesky and Start Page.

What each service needs as a minimum:

• Twitter, Mastodon, Threads and Bluesky: text only.
• Instagram and TikTok: an image or a video.
• Pinterest: an image, plus the board to pin to in metadata.pinterest.boardServiceId, which get_channel returns under metadata.boards[].serviceId.
• YouTube: a video, plus a title and category in metadata.youtube.

Twitter, Mastodon, Threads and Bluesky also take a thread, through metadata.<service>.thread. A threaded post sets both the top-level text and that array, the array holds every item in the thread, and the top-level text repeats the first item's text. Thread items attach media with the same asset shape as the post itself.

A link preview card is not an asset. It goes in metadata.<service>.linkAttachment on Facebook, LinkedIn, Threads and Bluesky, and it cannot be sent alongside a non-empty assets array. On Threads and Bluesky an individual thread item can carry one of its own.

It returns the post it saved: content, assets, service settings, tags, allowedActions, status and scheduling. An assistant does not need to read the post back to confirm what was stored.

Example prompt: "Add a post to my Buffer queue that says 'Excited to share our latest update!' for next Monday."

Changes an existing post. The post that results is validated as a whole, the same way a new one is, so anything you do send has to stand on its own rather than being merged field by field into the stored version.

Omission is how you keep what you are not changing, and it is the safer default. Leave assets out and the stored media stays; leave mode and dueAt out and the post keeps its slot; leave a service setting out and it stays as it is. Resending a value you did not mean to change risks writing a stale copy back over something that moved in the meantime.

What has to be complete is any field you do send, because these replace wholesale rather than merging: the assets array, a metadata.<service>.thread array, and a service metadata object, which still has to carry its required members, such as an Instagram post's type and shouldShareToFeed. Dropping one of those from an object you are sending will make the edit fail.

Scheduling follows the same pattern. Leaving schedulingType out keeps the post publishing the way it already does, and leaving mode and dueAt out keeps its current slot. Sending a mode reschedules the post even when it matches the one already set, so send one only when you mean to move the post.

An assistant does not need a fresh read to work this out. create_post and edit_post both return the post they saved, so one that already created or edited the post in this conversation can work from that response, and call get_post only when something it needs is missing or may have gone stale.

When you do replace the media, an existing asset's source becomes url and, on images only, its thumbnail becomes thumbnailUrl; a video never takes a thumbnailUrl and picks its frame through metadata.thumbnailOffset instead, on Instagram, TikTok and Pinterest. Service settings such as firstComment, linkAttachment, an Instagram geolocation and LinkedIn annotations are kept when you leave them out and cleared when you send null.

Editing a threaded post follows the same rule as creating one: send both the top-level text and the whole metadata.<service>.thread array, not just the item that changed.

It returns the post it saved, in the same shape create_post does.

Example prompt: "Move my Thursday LinkedIn post to Friday at 9am and shorten the opening line."

Deletes a post for good. Not every post can be deleted, so an assistant should check that deletePost appears in the post's allowedActions. list_posts and get_post both return that list, so this does not cost an extra lookup.

Example prompt: "Delete the draft I made this morning about the pricing update."

Adds up analytics across many posts over a date range and returns the totals and averages, rather than making an assistant pull every post and do the arithmetic itself.

The response always carries post count, reactions and comments. Other metrics, such as reach, impressions and engagement rate, appear only when every channel in the filter supports them. Metrics refresh once a day, so values can lag the social network by up to a day; metricsUpdatedAt reports how fresh the aggregate is, and is null when no post matched the filter. The date range can cover at most 365 days.

Example prompt: "How did my LinkedIn posts perform last month?"

Lists the ideas in an organization. Ideas capture a concept for a future post before it belongs to a channel. Each one returns its title, text, media, tags, target services, target date, board column and timestamps.

Example prompt: "What ideas do I have saved that are tagged for the product launch?"

Lists the columns on the ideas board, with each column's ID, name and lock status.

Example prompt: "What columns does my Buffer ideas board have?"

Saves a new idea. This captures content for later. It does not schedule or publish anything.

Idea media can be an image, a GIF, a link or a document. Video is not supported on ideas through the public API.

Example prompt: "Save an idea for a post about our new integration, tagged for Instagram and LinkedIn."

Lists the templates you can use in an organization. With no filter this returns all three kinds together: the public templates, your organization's internal ones, and your own private ones.

Example prompt: "What post templates can I use?"

Reads one template: its body, title, description, emoji, visibility and timestamps.

Example prompt: "Show me the full text of my product announcement template."

Creates a template in an organization. You can set it to private or internal. Public is curated by Buffer and cannot be set here.

Example prompt: "Turn this post into a template my whole team can reuse."

Changes a template. Only the fields you send are changed. You can edit templates you own, and internal templates in your organization if you are an admin or owner.

Example prompt: "Add a call to action line to my weekly recap template."

Deletes a template for good. You can delete templates you own, and internal templates in your organization if you are an admin or owner.

Example prompt: "Delete the old holiday sale template."

Returns the complete GraphQL schema for the Buffer API: every query, mutation, type and argument. This is only worth calling before execute_query or execute_mutation, since the tools above already cover the common jobs.

Takes no parameters.

Runs a read-only GraphQL query against the Buffer API.

Runs a GraphQL mutation against the Buffer API. This changes your data, so most clients will ask you to approve it.