Skip to main content
Glama
angheljf

social-media-mcp

by angheljf

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TWITTER_API_KEYYesYour Twitter API key
TWITTER_API_SECRETYesYour Twitter API secret
TWITTER_ACCESS_TOKENYesYour Twitter access token
TWITTER_ACCESS_SECRETYesYour Twitter access secret

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

Tools

Functions exposed to the LLM to take actions

NameDescription
post_to_xC

Post a message to X (formerly Twitter)

list_x_postsC

List X (formerly Twitter) posts

create_x_threadC

Create a thread on X (formerly Twitter)

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription
Social Media: XInformation about the X platform

TDQS

C2.6/5.0

Scored across 3 tools

Disambiguation2/5

The tools have significant overlap and unclear boundaries. 'create_x_thread' and 'post_to_x' both involve posting to X, with the distinction between a 'thread' and a 'post' not clearly defined in the descriptions, leading to potential confusion. 'list_x_posts' is more distinct but still part of the same ambiguous posting domain.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern with 'create_x_thread', 'list_x_posts', and 'post_to_x', all using snake_case. However, there is a minor deviation in the verb choice: 'create' vs. 'post' for similar actions, which slightly reduces consistency.

Tool Count2/5

With only 3 tools, the server feels too thin for a social media domain, lacking essential operations like updating, deleting, searching, or interacting with other platforms. This limited scope may hinder agents from performing common social media tasks effectively.

Completeness2/5

The tool surface is severely incomplete for a social media server. It focuses only on X (Twitter) with basic create and list operations, missing critical functions such as update, delete, reply, like, follow, or support for other platforms like Facebook or Instagram, leading to significant gaps in agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues