Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

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

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
social_networksB

List networks, capabilities and whether credentials are present.

social_postC

Post text (and optional media) to one network, or 'all'.

social_readC

Read recent posts/messages from a network.

social_scheduleC

Queue a post for a future time.

social_queueC

List queued jobs, or drain the ones that are due.

social_learnC

Learn (or verify) how to post on any site via the browser.

social_recipesB

List learned recipes and their version/confidence.

social_deleteC

Delete a post/message by id (network-dependent).

social_accountC

Prove which account/identity the credentials belong to.

social_ledger_selftestC

Append a test receipt and report where it went.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3/5.0

Scored across 10 tools

Disambiguation4/5

Most tools have clearly distinct purposes: posting, reading, scheduling, deleting, and discovering networks/accounts are easy to tell apart. The closest overlaps are social_schedule vs social_queue (queue a post vs list/drain jobs) and social_learn vs social_recipes (create/inspect learned recipes), but the descriptions make the boundaries reasonably clear.

Naming Consistency4/5

All names share a predictable 'social_' prefix and snake_case formatting, which makes the set feel cohesive. There is a minor mix of verb-style (social_post, social_read, social_delete) and noun-style (social_networks, social_queue, social_recipes) names, but this is still readable and mostly intuitive.

Tool Count5/5

Ten tools is well within the sweet spot for a social-posting automation server, and each tool maps to a concrete operation (publish, schedule, queue, read, learn, verify account, delete). Nothing appears redundant or purely decorative.

Completeness4/5

The surface covers the core lifecycle: discover networks, authenticate/verify accounts, post, schedule, queue, read, and delete, plus a learning mechanism for new sites. Minor gaps exist around editing/updating an existing post, reply/thread handling, and engagement metrics, but agents can work around these for typical posting workflows.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues