Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

threads_search

Search public Threads posts by query and sort results by top or recent. Returns the first page of public search results; no continuation cursor due login wall.

Instructions

Search public Threads posts. Returns the public first page of Threads search results for a query. sort supports top and recent; pagination_limited marks the logged-out login wall because search has no continuation cursor. Author and date filters in Threads require login and are not exposed here.

Input Schema

NameRequiredDescriptionDefault
qYesSearch query (1-100 characters)
sortNoResult order; defaults to top

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.13
    • addedInput schema / properties / sort
      Added value: +{
+  "description": "Result order; defaults to top",
+  "enum": [
+    "top",
+    "recent"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses that only the first page is returned, that there is no continuation cursor, and that pagination_limited signals the logged-out login wall. It stops short of stating the tool's own auth posture or any rate limits, but the login-wall and pagination constraints are exactly the behavioral context an agent needs.

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?

Four compact sentences that lead with the core purpose and then layer constraints. Slightly dense in the middle with the enum restatement, but nothing is padded and the most important information is 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?

There is no output schema, so the description must cover what comes back, and it does: it explains the first-page-only result and the meaning of pagination_limited. Combined with the filter-exclusion note, an agent has enough to call this correctly and interpret the response, though return value structure itself is left unspecified.

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 both q (length bound) and the sort enum fully documented in the schema, so the baseline is 3. The description's note that sort 'supports top and recent' merely restates the enum, and pagination_limited is a response field rather than a parameter, so no additional parameter meaning is added.

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 first sentence states a precise verb+resource ('Search public Threads posts') and the second scopes the result ('public first page of Threads search results for a query'). This clearly separates it from siblings like threads_profile_posts, threads_post, and threads_topic_search, which target profiles or topics rather than a query-driven post search.

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

Usage Guidelines3/5

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

It usefully rules out capabilities an agent might assume (author/date filters exist in Threads but require login and are not exposed), which steers usage. However, it never names an alternative tool or states the condition for choosing this over threads_topic_search or threads_profile_posts, so the routing guidance is only implied.

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

Deploy Server

Other Tools