postbuzz-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTBUZZ_API_KEY | Yes | Your post.buzz API key (sx_live_...). Can also be set via --api-key. | |
| POSTBUZZ_API_URL | No | API base URL. Can also be set via --api-url. | https://post.buzz/api |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_setupA | Verify the API key, connectivity, connected accounts, and quota. Run this first before any other tool. |
| describe_platformA | Per-platform publish field schemas and adapter capabilities. Call before create_post/create_comment to learn required fields. Offline — no API call. |
| get_organizationC | Plan, limits, and connected-account summary. |
| get_usageB | Monthly post usage, plan limit, and credit balance. |
| list_accountsB | Connected social accounts (id, platform, username). |
| get_accountB | One connected account: profile, follower count, token health (disconnectedAt / tokenExpiresAt). |
| connect_accountA | Build the OAuth authorize URL for a platform; the user opens it in a browser to connect. |
| disconnect_accountA | Disconnect an account. Cascades pending schedules, comment automation, inbox, goals, and agents; published history is kept. |
| refresh_accountB | Refresh an account's OAuth access token server-side. |
| list_account_toolsC | Per-account live lookups available for the account's platform (e.g. Reddit flairs, Pinterest boards). |
| run_account_toolA | Run a per-account lookup: reddit-flairs (input { subreddit }) or pinterest-boards (input {}). Use before creating posts that need a flair or board id. |
| create_postA | Create a post (saved as a draft — no scheduledAt). Call describe_platform first for per-platform required fields. |
| schedule_postB | Create a post scheduled for an ISO 8601 time (e.g. 2026-10-01T09:00:00Z). |
| list_postsC | List posts with optional filters and pagination. |
| get_postA | Fetch one post with its accounts (permalinks, overrides) and media. |
| update_postB | Partially update a post: caption, media, schedule (scheduledAt; null clears it → draft), status, poll, thread. |
| delete_postA | Delete a draft/scheduled post (published posts are kept). |
| retry_postB | Re-queue a post's failed schedules for another attempt. |
| reschedule_postC | Move a post's target time (ISO 8601). |
| create_commentA | Create a comment on a post by the given account. Omit scheduledAt to publish immediately; pass parentCommentId to reply to another scheduled comment. |
| list_commentsC | Scheduled comments for a post. |
| get_commentB | Fetch one scheduled comment. |
| update_commentA | Edit a pending comment's text and/or due time. |
| delete_commentC | Delete a pending comment. |
| retry_commentB | Publish a pending/failed comment now. |
| list_inboxC | Incoming comments, mentions, and DMs across accessible accounts. |
| reply_to_inbox_itemB | Reply to a comment/mention/DM. |
| edit_inbox_replyA | Edit a reply already sent (currently Facebook only — others return a platform error). |
| upload_mediaA | Upload media from a public URL or a local file path. Returns the media row whose id posts reference via mediaIds. |
| list_mediaC | List uploaded media. |
| get_mediaC | Fetch one media item. |
| delete_mediaB | Delete one media item. |
| delete_media_manyA | Delete several media items; reports per-id outcomes. |
| get_post_analyticsA | One post's metrics (likes, comments, reach, …). |
| get_account_analyticsC | An account's engagement summary over a window. |
| get_bulk_post_analyticsB | Analytics for up to 60 posts; per-post errors included. |
| refresh_analyticsA | Enqueue an async analytics backfill for a post or account (job id returned). |
| get_analytics_summaryC | Latest analytics row per accessible account in the window. |
| get_best_timesC | Recommended posting times from engagement history (optionally per account). |
| list_teamsC | Teams with their member accounts. |
| get_teamB | One team with its member accounts. |
| create_teamC | Create a team (optionally assigning accounts). |
| update_teamC | Rename/re-describe a team or reassign its accounts. |
| delete_teamB | Delete a team that no longer owns accounts. |
| add_team_accountC | Assign an account to a team. |
| remove_team_accountA | Remove an account from a team (reassigned to the default team). |
| create_post_csv_importB | Bulk-create posts from CSV text or a public CSV URL. Columns include caption and accountId. |
| list_post_csv_importsC | The caller's CSV import jobs with counts. |
| get_post_csv_importD | One import job's summary. |
| get_post_csv_import_rowsC | Per-row SUCCESS/FAILED results for an import job. |
| retry_post_csv_importB | Re-run an import job's failed rows. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 51 tools
Most tools follow a clear resource+action boundary (posts, comments, media, accounts, teams), and list/get pairs are standard CRUD distinctions. A few ambiguities remain—update_post can also move a schedule, making reschedule_post somewhat redundant, and there are several overlapping analytics retrieval tools—but descriptions generally keep them apart.
All 51 tools use a consistent snake_case verb_noun pattern, e.g. list_posts, create_post, delete_comment, refresh_account. Compound resources are also uniformly prefixed (post_csv_import), so the naming convention is highly predictable.
51 tools is far beyond the 25+ threshold and creates a heavy selection burden for an agent, even though the tools are grouped by domain. The breadth may be justified for a full social media platform, but as an MCP surface it is over-scoped and several convenience tools (delete_media_many, analytics variants, per-account tools) could be consolidated.
The server provides solid lifecycle coverage for posts, scheduled comments, media, accounts, teams, analytics, and CSV imports, including retries and bulk operations. Minor gaps exist—inbox actions are limited to reply/edit, published posts cannot be deleted/unpublished, and organization settings are read-only—but core workflows have no dead ends.