posthive
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTHIVE_API_KEY | Yes | API key from Posthive Settings → API Keys | |
| POSTHIVE_API_URL | No | Base URL of your Posthive API. Leave blank to use https://api.posthive.co |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_accountsA | List all connected social media accounts for this Posthive workspace. Returns account IDs, platforms, and display names. Use these IDs when creating posts. |
| create_postA | Create a post in Posthive. BY DEFAULT posts are saved as DRAFTS and require manual approval in the Posthive review queue before anything is published. Nothing is published automatically unless schedule_directly is explicitly set to true with a future scheduled_time. Use list_accounts to get valid account IDs before calling this tool. Each platform has its own character limit for both the post text and the first_comment — the request is rejected with a 400 if either exceeds it for any selected account: Bluesky 300, Threads/Mastodon/Pinterest 500, Instagram/TikTok 2200, Discord 2000, LinkedIn 3000, Telegram/Tumblr 4096, YouTube 5000, Nostr/Lemmy 10000, Twitter/X 25000, Facebook 63206. Check the content and first_comment length against the shortest limit among the selected platforms before calling, and warn the user if a caption (especially a long hashtag block) would be rejected. TikTok accounts require a video in media_urls (.mp4/.mov) plus tiktok_privacy_level, or the request is rejected with a 400. |
| get_postA | Get full details of a single post by ID, including per-platform publish status. |
| list_scheduled_postsB | List upcoming scheduled posts and drafts in the queue. |
| approve_draftA | Approve a draft post and schedule it for publishing at a specific time. Promotes a draft to the scheduled queue — it will publish at scheduled_time without further approval. Only works on posts with status 'draft'. |
| update_postA | Update content or scheduled time of a queued or draft post. Only pending/draft posts can be updated. |
| duplicate_postB | Clone an existing post as a new draft. Copies content, accounts, and per-account overrides. |
| delete_postA | Delete a pending or draft post from the queue. |
| list_templatesA | List all saved post templates in this Posthive workspace. |
| create_from_templateA | Create a draft post using a saved template as the base content. You can override the text before saving. Use list_templates to get template IDs. |
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 10 tools
Each tool targets a distinct verb+resource pair: create/get/update/delete/duplicate post, accounts and templates listing, draft approval. The only minor overlap is between update_post (changing scheduled_time) and approve_draft (scheduling a draft), but the descriptions clarify that approve_draft only works on drafts and promotes them to the queue.
All ten tools follow a strict snake_case verb_noun pattern (create_post, get_post, update_post, delete_post, duplicate_post, list_accounts, list_templates, approve_draft), with no mixed conventions.
Ten tools is well within the ideal 3-15 range and each one maps to a real operation in the post lifecycle (author, review, schedule, duplicate, delete, plus supporting account/template lookups).
Core post CRUD plus draft approval is covered, but template support is one-sided: there is list_templates and create_from_template with no create_template, update_template, or delete_template. There is also no way to list or inspect already-published posts beyond get_post by ID, which leaves reporting/history as a dead end.