Skip to main content
Glama

socialbridge-mcp

by io.github.IsaiahDupree

Get an account's recent posts

social_posts
Read-onlyIdempotent

An account's recent posts / videos / tweets / threads / pins as the unified Post[] schema (id, url, author, text, createdAt, like/comment/share/view counts, mediaType, mediaUrls, hashtags), tagged with its platform. Keyless on Instagram, TikTok, YouTube, Pinterest, Snapchat, and Threads. Twitter/X, Reddit, and Facebook need operator-side credentials; LinkedIn is quarantined. For a keyless Reddit history pull use reddit_history.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results, clamped 1-100. Default 20.
cursorNoOpaque pagination cursor from a previous response (where the platform supports paging).
platformYesTarget social network.
usernameYesAccount handle / username (without @).

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety profile is covered. The description adds valuable context beyond annotations: platform-specific credential requirements, LinkedIn quarantine, and the unified output schema. It does not cover error handling or rate limits, so a 4 is appropriate rather than 5.

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?

The description is compact and information-dense, leading with the core function, then enumerating the output schema, keyless platforms, credential requirements, and a specific alternative in a few sentences. No redundant or filler content.

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

Completeness5/5

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

For a multi-platform read-only tool with complexity around credentials and output unification, the description is exceptionally complete. It explicitly describes the unified Post[] schema, lists which platforms require credentials, flags LinkedIn as quarantined, and even names the sibling tool for a specific use case. This gives an agent sufficient context to select and invoke the tool correctly.

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

Parameters3/5

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

Schema description coverage is 100%, with all four parameters well-documented including the platform enum, username without '@', limit clamping, and cursor semantics. The description adds platform context that indirectly affects the 'platform' parameter but does not alter understanding of parameter syntax or formats, so the baseline 3 applies.

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 it retrieves an account's recent posts across multiple platforms with a unified Post[] schema, listing exact fields. It distinguishes itself from sibling tools by explicitly naming reddit_history as an alternative for keyless Reddit pulls, and the title 'Get an account's recent posts' is specific.

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

Usage Guidelines5/5

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

The description explicitly states which platforms are keyless (Instagram, TikTok, YouTube, Pinterest, Snapchat, Threads) and which require operator-side credentials (Twitter/X, Reddit, Facebook), and notes LinkedIn is quarantined. It also directly recommends using reddit_history for keyless Reddit access, providing clear when-to-use and when-not-to-use guidance.

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