Skip to main content
Glama
social-watch-mcp

social-watch-mcp

by denis1stomin

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
X_API_KEYNoOne of the four X_* values for a separate Read-only X app.
ITCH_API_KEYNoitch.io API key.
X_API_SECRETNoOne of the four X_* values for a separate Read-only X app.
THREADS_TOKENNoLong-lived Threads API token (renew every 60 days).
X_ACCESS_TOKENNoOne of the four X_* values for a separate Read-only X app.
YOUTUBE_API_KEYNoYouTube API key.
YOUTUBE_CHANNEL_IDNoYouTube channel ID.
X_ACCESS_TOKEN_SECRETNoOne of the four X_* values for a separate Read-only X app.

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": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
accountsB

Which platforms are set up, and each profile (name, handle, followers/subscribers where the API gives them).

recent_postsA

Latest posts (Threads, X), games (itch.io) or videos (YouTube): id, date, shortened text, link. On X every returned post costs credits, so keep limit small.

post_statsA

Numbers for one post/game/video by id: views, likes, replies, reposts/shares, downloads, as far as the platform gives them.

repliesB

Replies, comments and mentions to read: text, author handle, date, link. since = ISO date or Unix seconds.

totalsC

Account-level numbers: followers, total views, downloads, purchases...

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 5 tools

Disambiguation4/5

Each tool targets a clearly different scope: post_stats is per-item metrics, totals is account-level aggregates, recent_posts is the newest content feed, replies is incoming engagement, and accounts is configuration/profile info. The only mild overlap is post_stats vs totals (per-post vs per-account numbers), but the descriptions explicitly frame that distinction, so misselection is unlikely.

Naming Consistency4/5

All five names are lowercase snake_case and follow a consistent noun-phrase style (post_stats, recent_posts, replies, accounts, totals). No camelCase or mixed verb styles, though the set lacks an explicit verb prefix, so the pattern is consistent but slightly generic.

Tool Count5/5

Five tools is well within the ideal 3-15 range and each covers a distinct facet of social monitoring (per-post metrics, feeds, replies, accounts, aggregates). No tool feels redundant or padded, and nothing obviously missing at this count.

Completeness4/5

The read-only monitoring lifecycle is largely covered: discover content (recent_posts), drill into a post (post_stats), read engagement (replies), list profiles (accounts), and aggregate (totals). Minor gaps include no historical/time-series trend query, no per-post reply filtering or lookup of a single post's full text, and limited pagination options beyond 'since' and 'limit'.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues