Skip to main content
Glama
socialappsceduler-eng

FastSocial MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
FASTSOCIAL_API_KEYYesYour FastSocial API key. Create one at Settings → API Keys in your FastSocial account.

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
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_account_infoA

Get the current FastSocial account info including connected platforms, plan, and subscription status.

schedule_postB

Schedule a social media post to be published at a specific time. Supports Facebook, Instagram, Twitter/X, LinkedIn, YouTube, TikTok, and Pinterest.

list_postsA

List scheduled, published, draft, or failed posts. Can filter by platform or status.

get_postC

Get details of a specific post by its ID.

update_postB

Update the text, scheduled time, or status of an existing post.

delete_postC

Delete a post by its ID.

get_analyticsA

Get analytics summary for the account: total posts, breakdown by status, breakdown by platform, and posts created/published this month.

list_connected_platformsA

List all connected social media platforms for this account.

list_clientsA

List clients (for reseller accounts). Returns all clients under the reseller, or just the current client for single-account keys.

list_mediaB

List uploaded media files in the media library.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 10 tools

Disambiguation5/5

Each tool serves a distinct purpose: CRUD for posts, account info, analytics, media library, platforms, and clients. No overlap or ambiguity between tool functions.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern (e.g., delete_post, get_account_info, list_media). No mixing of styles or inconsistent verbs.

Tool Count5/5

10 tools cover the core domain of social media post management, account information, and analytics without unnecessary bloat. The number feels well-scoped for the server's purpose.

Completeness4/5

Full CRUD for posts, plus account, analytics, platforms, media listing, and client management. Missing media upload or platform connection/disconnection, but these are minor gaps for the primary use case.

Maintenance

ActivityStale
ResponsivenessNo issues