Skip to main content
Glama
Sign In

API Direct

by io.apidirect
OverviewDiscussionsAdmin

Search Threads Posts

search_threads
Read-only

Search Threads (Meta) posts by keyword. Returns post text, author, engagement metrics (likes, replies, reposts, quotes, reshares), media, link previews, permalinks and Threads' AI label (ai_label). About 20 posts on the first page and 10 on each later page. Billed $0.006 per page.

Input Schema

NameRequiredDescriptionDefault
pagesNoNumber of pages to fetch, 1-200 (default: 1). The first page returns about 20 posts and later pages about 10
queryYesSearch keyword (max 500 characters)
get_sentimentNoAdd AI sentiment analysis (Plutchik emotions, dominant_emotion, intensity, and positive/negative/neutral polarity) to each result. Adds a small surcharge per page, or per request on single-request endpoints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / pages
      Added value: +{
+  "default": 1,
+  "description": "Number of pages to fetch, 1-200 (default: 1). The first page returns about 20 posts and later pages about 10",
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / get_sentiment / description
      Previous value: -"Add AI sentiment analysis (Plutchik emotions, dominant_emotion, intensity, and positive/negative/neutral polarity) to each result. Adds a small per-page surcharge."New value: +"Add AI sentiment analysis (Plutchik emotions, dominant_emotion, intensity, and positive/negative/neutral polarity) to each result. Adds a small surcharge per page, or per request on single-request endpoints."
  3. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, non-destructive, open-world search operation. The description adds useful behavioral context beyond that: returned fields, first-page versus later-page result counts, and per-page billing of $0.006. It does not discuss rate limits or authentication, but the added cost and pagination details are meaningful.

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, then efficiently covers return fields, pagination behavior, and cost. Every sentence contributes useful information with no wasted language.

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?

There is no output schema, so the description appropriately enumerates the returned post data, including engagement metrics, media, links, permalinks, and ai_label. Combined with the annotations and complete schema coverage, it provides enough context to invoke the tool 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 description coverage is 100%, so all three parameters are already documented in the input schema. The description reinforces page sizing and mentions cost, but it does not add parameter semantics beyond what the schema provides.

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?

The description states a specific verb and resource: 'Search Threads (Meta) posts by keyword.' It clearly identifies the platform and content type, but it does not explicitly distinguish this keyword-search tool from siblings like threads_user_posts or search_threads_users.

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?

The phrase 'by keyword' implies when to use it for topical discovery rather than user-timeline retrieval. However, the description gives no explicit when-to-use versus alternatives guidance, nor does it mention exclusions or prerequisites.

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

All API Direct 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