Crawlora MCP

threads_search

Read-only

Search public Threads posts with q (1-100 characters) and optional sort top or recent; top is default and recent maps to Threads' Recent filter. Results include authors and topic tags for profile discovery. Logged-out search has no cursor; check pagination_limited. Use threads_topic_search for topic tags, threads_profile_topics to discover tags, or threads_profile_posts for one profile.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "threads_search"
  }
}

Input Schema

Name	Required	Description	Default
`q`	Yes	Search query containing 1 to 100 characters.
`sort`	No	Result order: top or recent. Defaults to top.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 19, 2026

addedInput schema / properties / q

Added value: +{
+  "description": "Search query containing 1 to 100 characters.",
+  "type": "string"
+}

removedInput schema / properties / query

Removed value: -{
-  "description": "Search query containing 1 to 100 characters.",
-  "type": "string"
-}

addedInput schema / properties / sort

Added value: +{
+  "description": "Result order: top or recent. Defaults to top.",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "q"
+]
```

First observedOct 5, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations cover readOnlyHint and openWorldHint, and the description adds real behavioral context: logged-out search returns no cursor and the agent should check pagination_limited. It also notes that results carry authors and topic tags. It does not detail rate limits or result caps, but the pagination caveat is a genuinely useful disclosure beyond the annotations.

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?

Front-loaded with the core action and parameters, then routing. Every sentence carries information, though the description is dense and could trim the parenthetical query-length repeat that the schema already states.

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?

An output schema exists, so return values need not be described; the description still adds useful notes on result contents and the pagination limitation. For a two-parameter search tool this is nearly complete, with only minor gaps around result counts or rate 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%, so both parameters (q and sort) are already documented. The description adds the semantic mapping that 'recent' corresponds to Threads' Recent filter and restates the default of top, which is minor added value over the schema. Baseline 3 is appropriate.

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?

States a specific verb (Search) and resource (public Threads posts) with scope details (public posts, query length, sort). It explicitly names three sibling tools and the conditions that select them, so an agent can differentiate without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit routing: threads_topic_search for topic tags, threads_profile_topics to discover tags, threads_profile_posts for a single profile. This tells the agent both when this tool applies and which alternatives to pick for adjacent needs.

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

All Crawlora MCP tools Inspect

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

Need Help?