Skip to main content
Glama

socialbridge-mcp

by io.github.IsaiahDupree

Get comments / replies on a post

social_comments
Read-onlyIdempotent

Comments / replies on one post as the unified Comment[] schema, tagged with its platform. Provide url OR postId. Keyless on TikTok, YouTube, and Threads (and a single tweet via syndication on Twitter/X). Instagram, Reddit, and Facebook need operator-side credentials; Snapchat comments are not supported keyless; LinkedIn is quarantined.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoPost URL. Provide url OR postId.
limitNoMax results, clamped 1-100. Default 20.
cursorNoOpaque pagination cursor from a previous response (where the platform supports paging).
postIdNoPlatform-native post id. Provide url OR postId.
platformYesTarget social network.

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses extensive behavioral details beyond annotations: which platforms support keyless access (TikTok, YouTube, Threads, Twitter/X via syndication), which require credentials (Instagram, Reddit, Facebook), Snapchat's lack of keyless support, and LinkedIn quarantine. These are non-obvious and add significant value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core purpose, followed by a compact enumeration of platform conditions. No redundant or unnecessary text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Covers core usage and major platform caveats, but omits pagination behavior (cursor) and rate limits. Given the parameter schema documents the cursor and the annotations indicate read-only/idempotent behavior, this is acceptable for a read-only tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Adds the 'url OR postId' constraint to clarify mutual exclusivity, which is not fully explicit in the schema. Also mentions the unified Comment[] schema. Since the schema already describes all parameters, this is incremental but meaningful.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Comments / replies on one post' with a specific resource (post) and output ('unified Comment[] schema'), distinguishing it from sibling tools like social_posts or social_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides clear usage context: 'Provide url OR postId' and enumerates platform-specific credential requirements. It does not explicitly name alternative tools, but the single-post scope and platform caveats imply appropriate usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All socialbridge-mcp toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

Most tools target distinct resources/actions, but there is some overlap: social_posts and reddit_history both return Reddit posts, social_search and search_all both perform searches, and snapchat_spotlight overlaps with social_posts for Snapchat. However, descriptions explicitly cross-reference and clarify when to use each, so misselection is unlikely.

Naming Consistency4/5

The naming generally follows a snake_case pattern with a resource noun, using either a social_ prefix (social_posts, social_comments) or a platform-specific prefix (facebook_ads, reddit_history, threads_post). The exception is search_all, which breaks the pattern and is less noun-like compared to others.

Tool Count5/5

With 10 tools covering profiles, posts, comments, search, and platform-specific features (ads, transcripts, spotlight), the count is well-scoped for a multi-platform social data retrieval server. Each tool serves a clear purpose and the set is not bloated.

Completeness4/5

The tool set covers core read operations across major platforms, including profile, posts, comments, and search. A notable gap is the lack of a generic way to fetch a single post by URL/ID across all platforms (only threads_post offers this specifically), which may require workarounds in some use cases.

Resources