PostWire
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTWIRE_API_KEY | Yes | Your PostWire API key. Get one at https://postwire.io/dashboard.html |
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 |
|---|---|
| post_to_socialA | Publish a post (optionally with a photo or video) to one or more social platforms via PostWire. Connect accounts first at https://postwire.io/dashboard.html. Returns per-platform results. |
| list_platformsA | List the social platforms PostWire supports and the fields each needs. |
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 2 tools
The two tools have completely distinct purposes: one lists supported platforms and their fields, the other posts content. There is no ambiguity or overlap.
Both tools use a consistent verb_noun pattern: list_platforms and post_to_social, making the naming predictable and clear.
With only 2 tools, the server is minimal but well-scoped for its focused domain of posting social media content via PostWire. The count is slightly thin but reasonable.
The tools cover the core functionality of listing supported platforms and posting content. Missing features like post history or schedule management are minor gaps for this server's stated purpose.