Skip to main content
Glama
webdata-tools-mcp

webdata-tools-mcp

Get Threads profiles, posts and replies

get_threads_posts
Read-onlyIdempotent

Public Threads (by Meta) data from profiles, post links or search words: profile details with followers, bio and links, latest posts with text, images and video, likes, replies, reposts, quotes and shares, and optionally the replies under…

Instructions

Public Threads (by Meta) data from profiles, post links or search words: profile details with followers, bio and links, latest posts with text, images and video, likes, replies, reposts, quotes and shares, and optionally the replies under each post. No login. Useful for social listening, creator research and brand monitoring. Runs the Apify Actor tacps126/threads-scraper on your Apify account (about $0.0015 per profile or post, $0.001 per reply; spend per call is capped at $0.5).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_threads_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
queriesNoSearch words, e.g. ["electric cars"].
profilesNoUsernames, profile links or post links, e.g. ["nasa"].
max_itemsNoMaximum results to return (default 100, max 2000). Cost scales with this.
extra_inputNoAdvanced: extra Actor input fields, merged over the defaults.
newest_firstNoFor searches: newest posts instead of top posts.
replies_per_postNoReplies to read under each post (0 = none).
posts_per_profileNoLatest posts to read per profile.

Output Schema

NameRequiredDescriptionDefault
toolYesName of the tool that produced the result.
countYesNumber of records the Actor returned.
itemsYesThe records. Long text fields are shortened to 600 characters.
shownYesNumber of records included in `items` (can be lower than count when the result is long).
truncatedYesTrue when records were left out to keep the result short; ask for fewer items.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.18.0

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already mark it read-only, idempotent, and non-destructive, and the description adds genuinely new operational context: no login required, it runs the tacps126/threads-scraper Actor on your own Apify account, per-item pricing, and a $0.5 per-call spend cap. Cost exposure and the account-side execution model are exactly the behavioral facts an agent cannot get from annotations or schema.

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?

It is one dense paragraph that front-loads the resource and payload before moving to cost and execution details, and each clause carries information. The enumeration of post metrics is slightly list-heavy, but nothing is truly wasted.

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 7-parameter, nested-input tool with an output schema, the description covers scope, inputs, cost model, and execution environment, and the output schema handles return values. An agent has everything needed to decide and call 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?

Schema coverage is 100%, so every parameter is already documented, including the cost-scaling note on max_items and the 0 = none convention for replies_per_post. The description mostly restates what the schema covers (usernames/links, replies under each post) without adding format or constraint detail beyond it, so the baseline 3 applies.

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 opens with a specific verb+resource: public Threads data from profiles, post links, or search words, and enumerates exactly what is returned (profile details, posts, likes, replies, reposts, quotes, shares). This is unambiguous and clearly distinct from sibling tools like get_pinterest_pins or get_facebook_pages.

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 names the three input modes (profiles, post links, search words) and three concrete use cases (social listening, creator research, brand monitoring), giving an agent clear context for selection. It does not explicitly state when to avoid this tool or name a specific alternative, which keeps it just 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.