Skip to main content
Glama
Sign In

Pullwire

by dev.pullwire
OverviewDiscussionsAdmin

Threads Scraper

threads
Read-only

Scrape public Threads posts by keyword search, profile or post URL: text, author, likes, replies, reposts, images, videos, links, mentions, profile details and the first page of replies. No login, no browser. Costs 1 credit per result; failed items are free.

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": "threads"
  }
}

Input Schema

NameRequiredDescriptionDefault
postUrlsNoLinks to single Threads posts. Returns the post and, if enabled, its replies.
usernamesNoUsernames or profile URLs. Returns the profile details and its latest public threads (Threads shows ~5 without an account).
maxResultsNoStop after this many posts in total. Empty: no extra cap.
searchQueriesNoKeywords or #hashtags to search on Threads. Each search returns the top ~20 matching threads (what Threads shows without an account).
includeRepliesNoFor post URLs: also return the author’s follow-up posts and the first page of replies (~10, what Threads shows without an account).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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, open-world, and non-destructive behavior. The description adds meaningful operational context beyond them: 'No login, no browser' clarifies access constraints, and 'Costs 1 credit per result; failed items are free' discloses the billing and failure model.

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 front-loaded with the core action and resource, followed by a compact list of returned data and two short operational sentences. Every sentence adds useful information with no wasted wording.

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 does well by enumerating the returned fields and clarifying input modes, cost, and access constraints. It does not cover pagination mechanics or rate limits beyond the schema's built-in caps, leaving a minor gap for a scraping tool.

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 parameter definitions already explain postUrls, usernames, searchQueries, maxResults, and includeReplies in detail. The description adds a high-level overview of input modes but no additional parameter syntax or constraints beyond what the schema 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 uses a specific verb and resource: 'Scrape public Threads posts by keyword search, profile or post URL.' It also enumerates the returned fields and explicitly names the three input modes, making the tool's scope unmistakable and distinguishing it from sibling scrapers by platform.

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 clear usage context by mapping each input mode (keyword search, profile, post URL) to expected output. It does not explicitly say when to choose a sibling tool or when not to use this one, so it falls just short of full alternative-routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Pullwire toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources