Skip to main content
Glama

socialbridge-mcp

by io.github.IsaiahDupree

Reddit full history (keyless)

reddit_history
Read-onlyIdempotent

Keyless full-history pull via Arctic Shift — a user's or subreddit's posts, or a keyword search across Reddit history, returned as the unified Post[]. Provide at least one of username, subreddit, or q. Optional before/after bound the window by epoch-seconds or ISO timestamp.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoKeyword to search across history.
afterNoReturn items created after this epoch-seconds / ISO timestamp.
limitNoMax results, clamped 1-100. Default 25.
beforeNoReturn items created before this epoch-seconds / ISO timestamp.
usernameNoReddit username (without u/).
subredditNoSubreddit (without r/).

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, and the description adds key context: keyless access (no auth), reliance on Arctic Shift as the data source, and a unified Post[] return shape. No contradictions with annotations, and it goes beyond what annotations provide.

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 two sentences, front-loading the core purpose ('Keyless full-history pull via Arctic Shift') before detailing scope and parameter requirements. Every sentence contributes value with no redundancy or fluff.

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?

For a tool with three distinct modes, no output schema, and six optional parameters, the description covers the essential return shape (unified Post[]), parameter requirements, and time-bounding options. It omits details like pagination beyond the limit parameter and behavior when multiple filters are combined, but these are minor gaps given the schema and annotations.

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?

Schema coverage is 100%, so baseline is 3. The description adds the crucial requirement that at least one of username, subreddit, or q must be provided, which is not in the schema's required list. It also clarifies the before/after window accepts both epoch-seconds and ISO timestamps, though the schema already indicates this.

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 identifies the tool as a keyless full-history pull via Arctic Shift, covering user posts, subreddit posts, or keyword search. It distinguishes itself from siblings like social_search or social_posts by emphasizing 'full history' and 'keyless' access.

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 usage context: 'Provide at least one of username, subreddit, or q' and optional before/after bounds. It does not explicitly name alternative tools, but the full-history and keyless framing implies when it is appropriate compared to more limited search tools.

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