Skip to main content
Glama

socialbridge-mcp

by io.github.IsaiahDupree

Search every network at once

search_all
Read-onlyIdempotent

The wedge no incumbent offers: fan one search query out across the requested platforms (default: all keyless, non-disabled) in parallel, merge the unified Post[], and tag each result with its platform. Gated / disabled / unsupported / throttled engines are listed under "skipped" with an honest reason — the call still returns whatever came back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query.
limitNoMax results, clamped 1-50. Default 10.
platformsNoComma-separated subset of platforms to query (e.g. "tiktok,youtube,threads"). Omit for all keyless, non-disabled platforms.

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare read-only/non-destructive behavior. The description adds valuable behavioral details: parallel execution, merging results into Post[], tagging platform, and the 'skipped' list with reasons for gated/disabled/unsupported/throttled engines. It also discloses partial results are returned even if some fail.

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

Conciseness4/5

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

The description is a single dense sentence, front-loaded with purpose. The phrase 'The wedge no incumbent offers' is marketing fluff rather than functional content, slightly reducing conciseness, but the rest is efficient and information-rich.

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?

No output schema exists, so the description must explain return values. It covers the merged Post[] with platform tags, the 'skipped' list with reasons, and the guarantee of returning whatever results came back – sufficient for an aggregator tool of this complexity.

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%, so the baseline is 3. The description adds no new parameter meaning beyond the schema; it mentions 'default: all keyless, non-disabled' for platforms, but the schema already says 'Omit for all keyless, non-disabled platforms.' The 'clamped 1-50' for limit is already encoded in min/max.

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 specifies the action: 'fan one search query out across the requested platforms' and 'merge the unified Post[]'. It distinguishes itself from siblings by covering multiple platforms at once, and the unique scope is evident.

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 conveys a clear use case: cross-platform search in parallel. It implies this is the go-to for multi-platform queries, though it doesn't explicitly state when to prefer sibling tools for single-platform searches or provide exclusions. Context is clear but not fully explicit.

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