Skip to main content
Glama
DataForB2B

DataForB2B MCP Server

Official
by DataForB2B

Search Social Posts

search_posts
Read-onlyIdempotent

Search social posts by keyword on LinkedIn, Twitter, or Reddit to find buying intent, then attach engagers as leads for targeted outreach.

Instructions

Search social posts by keyword on LinkedIn, Twitter/X, or Reddit — or target a single post by URL. Great for intent signals: find people talking about a topic, then use include to attach the post's engagers (each reactor / commenter is a lead, with their profile).

Two modes:

  1. Keyword search: set keyword (+ optional filters).

  2. Single post: set post_url (with include to get its engagers).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of posts to return.
matchNo'strict' (default) keeps only posts whose text actually contains the searched terms; 'loose' returns the platform's raw results.strict
offsetNoPagination offset.
includeNoAttach engagers to each returned post: any of ['reactions', 'comments']. Each engager is a lead. (Reddit exposes comments only — no upvoters.)
keywordNoSearch keyword in post content. Required unless `post_url` is set.
sort_byNoSort order.date_posted
platformNoPlatform to search.linkedin
post_urlNoTarget a single post by URL instead of a keyword search. Use with `include` to get its engagers.
subredditNoReddit only: restrict the search to one subreddit (e.g. 'SaaS').
date_postedNoFilter by post freshness.
from_memberNoLinkedIn only: posts authored by this member URN (e.g. ACoAABxxxxxx).
content_typeNoLinkedIn only: filter by content type.
author_companyNoFilter by the post author's company name.
author_industryNoFilter by the post author's industry.
author_job_titleNoFilter by the post author's job title.
engagement_countNoMax engagers per type, per post, when `include` is set.
from_organizationNoLinkedIn only: posts authored by this organization id (numeric).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNoNumber of posts returned in this page.
errorNoHTTP-style status code, present only when the call failed.
totalNoNumber of posts matching the search (lower bound when has_next is true).
detailNoError message, present only when the call failed.
offsetNoPagination offset of this page.
resultsNoPost objects (author, text, engagement counts, and engagers when `include` is set).
has_nextNoWhether more results are available.
credits_usedNoCredits consumed by this search.
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. The description adds behavioral context beyond this: 'each reactor / commenter is a lead, with their profile' and that include attaches engagers, which is not evident from annotations alone.

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 concise paragraphs, front-loaded with the core action, followed by a clear list of modes. No filler; every sentence contributes to understanding purpose or usage.

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 17 parameters and an output schema, the description covers primary use cases (keyword search and single-post retrieval with leads). Platform-specific limitations like Reddit's comment-only engagers are in the schema. The description is sufficient for an agent 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.

Parameters4/5

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

Schema description coverage is 100% for all 17 parameters, so the baseline is 3. The description adds high-level value by explaining the keyword vs post_url modes and the include/engager workflow, which helps an agent understand how parameters work together beyond individual schema entries.

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?

Description clearly states 'Search social posts by keyword on LinkedIn, Twitter/X, or Reddit — or target a single post by URL' with specific verb+resource+scope. It distinguishes from sibling tools like search_people and search_company by focusing on posts and lead generation from engagers.

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?

Provides clear context: 'Great for intent signals' and explains two modes (keyword vs URL) and the include option. However, it does not explicitly name alternatives or exclusion criteria like 'use search_people for profiles,' so it stops 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.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/DataForB2B/dataforb2b-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server