Skip to main content
Glama

socialbridge-mcp

by io.github.IsaiahDupree

Facebook / Meta Ad Library

facebook_ads
Read-onlyIdempotent

Meta (Facebook/Instagram) Ad Library records as the unified Ad[] (id, pageName, adCreativeBody, adSnapshotUrl, startDate, currency, spend + impression ranges). Provide q OR pageId. GATED — needs operator-side FACEBOOK_ACCESS_TOKEN (with ads_read); returns credentials_required until set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search across ad creative. Provide q OR pageId.
limitNoMax results, clamped 1-100. Default 25.
pageIdNoAdvertiser Page id. Provide q OR pageId.
countryNoISO-3166 alpha-2 country (upper-cased server-side). Default US.

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only/idempotent/non-destructive, and the description adds the auth requirement and the 'credentials_required until set' behavior, which goes beyond the annotations. It doesn't mention pagination, but for a read-only retrieval tool this is sufficient extra 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?

Two sentences: the first describes the resource and output, the second covers the query options and auth requirement. Every clause carries distinct, useful information with no filler, and the key details are front-loaded.

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?

With no output schema, the description provides a list of output fields (id, pageName, etc.), which is valuable. It also notes the gate/auth failure mode. It leaves limit clamping and country default to the schema, which is acceptable since the schema documents them, and the overall picture is complete enough for an agent to anticipate behavior.

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 coverage is 100% with descriptive parameter comments, so baseline is 3. The description repeats the q OR pageId constraint already present in the schema, but adds no new format details or clarifications. It does not add meaningful value beyond what the schema already provides.

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 retrieving Meta Ad Library records, specifying the exact output shape (Ad[] with fields). It is distinct from sibling tools by naming the platform (Facebook/Instagram) and the specific data source, so an agent knows exactly when to select it.

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?

It gives direct usage instructions ('Provide q OR pageId') and states a key prerequisite (operator-side face_ACCESS_TOKEN with ads_read). It doesn't explicitly mention alternatives, but the platform-specific scope strongly implies when this tool is appropriate relative to the social_search siblings.

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