Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

threads_topic_search

Search public Threads topic tag posts with the canonical query and numeric tag id, returning the first page and flagging pagination_limited when a login wall blocks more.

Instructions

Search posts for a public Threads topic tag. Returns the public first page of posts for a topic tag. Discover the required tag_id and its canonical query name from /threads/profile/{username}/topics or a post's topic metadata. Topic results have no logged-out continuation cursor; pagination_limited marks the login wall for more results.

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>",
      "tag_id": "<tag_id>"
    },
    "name": "threads_topic_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesCanonical topic query from a profile topic's `name` or a post topic's `search_query`
tag_idYesNumeric Threads topic tag id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.13

TDQS

A4/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 useful work: it discloses that only the public first page is returned, that there is no logged-out continuation cursor, and that pagination_limited signals the login wall. It omits auth requirements and rate limits, but the pagination/login-wall disclosure is substantive.

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?

Three sentences, front-loaded with the action and scope, then prerequisites, then the pagination caveat. Slightly redundant between the first two sentences ('Search posts for a public Threads topic tag' vs 'Returns the public first page of posts for a topic tag'), but otherwise efficient.

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?

No output schema or annotations exist, and the description covers purpose, how to obtain both required inputs, and the pagination limitation (including the pagination_limited signal). Return field shapes beyond that are unstated, but the calling-critical information is present.

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 coverage is 100%, so the baseline is 3, but the description adds real value by explaining where both required values come from — tag_id from profile topics or a post's topic metadata, and q as the canonical name/search_query. That source-of-truth guidance exceeds the schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (Search) and resource (posts for a public Threads topic tag), and scopes it to the public first page. It is clearly distinct from generic threads_search in intent, though it never names or contrasts with that sibling explicitly.

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?

Gives a concrete prerequisite path: obtain the required tag_id and canonical q from /threads/profile/{username}/topics or a post's topic metadata. It does not state when to prefer this over threads_search or threads_profile_posts, so the routing guidance is incomplete.

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