Skip to main content
Glama

socialbridge-mcp

by io.github.IsaiahDupree

Get a social profile

social_profile
Read-onlyIdempotent

Fetch one account profile from any supported network as the unified Profile schema (id, username, displayName, bio, url, followers, following, postCount, verified, avatarUrl, externalUrl), tagged with its platform. Keyless on Instagram, TikTok, YouTube, Pinterest, Snapchat, and Threads. Twitter/X, Reddit, and Facebook need operator-side credentials (returns credentials_required until set); LinkedIn is quarantined (platform_disabled).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
platformYesTarget social network.
usernameYesAccount handle / username (without @).

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnly/idempotent hints in annotations, the description discloses credential requirements (keyless vs credentials_required), platform disabling (platform_disabled for LinkedIn), and enumerates the exact fields returned in the unified Profile schema. This provides meaningful behavioral context.

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, with three sentences each serving a purpose: stating the core function, listing the schema fields, and covering platform-specific execution. No unnecessary words or repetition.

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 simple two-parameter read tool with no output schema, the description is fully self-contained: it explains what the tool returns (unified Profile schema), how to invoke it (platform and username), and important operational caveats (credentials and disabled platform). The agent has everything needed to select and use 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?

The input schema already describes both parameters fully (platform enum and username format), achieving 100% schema coverage. The description adds no additional parameter-level meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 starts with 'Fetch one account profile from any supported network', clearly stating the action and resource. It also specifies the unified Profile schema and platform tagging, which distinguishes it from sibling tools like social_posts or social_comments.

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?

The description provides clear context on platform availability: it names which platforms are keyless, which require credentials, and which are disabled. However, it does not explicitly name alternatives or state when not to use this tool, so it falls short of a 5.

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