Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search Threads

search_threads

Find Threads posts by keyword to research trends and audience voice, returning compact JSON with author, likes, and link.

Instructions

Organic Threads keyword search (/v1/threads/search) — short-form text/social posts for trend + voice research. Returns compact JSON {desc, author, handle, likes, link, cover} per post. Spends about a credit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNomax posts returned (1–25, default 8)
queryYeskeyword to search Threads for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.161
    • changedOutput schema / (root)
      Previous value: -{
-  "$schema": "http://json-schema.org/draft-07/schema#",
-  "additionalProperties": false,
-  "properties": {
-    "found": {
-      "description": "total posts found",
-      "type": "number"
-    },
-    "posts": {
-      "description": "the compact post objects ({desc, author, handle, likes, link, cover})",
-      "items": {},
-      "type": "array"
-    }
-  },
-  "type": "object"
-}New value: +null
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations cover the safety profile (destructiveHint=false, openWorldHint=true), and the description adds genuinely useful context beyond them: the response shape and the cost ("Spends about a credit"), which matters for a metered open-world search. It stops short of describing rate limits or result ordering.

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?

Two tight sentences with zero filler; endpoint, corpus, return fields, and cost are front-loaded in that order. Every clause carries information an agent can act on.

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 usefully enumerates the returned fields (desc, author, handle, likes, link, cover), and the cost note rounds out the picture for a paid, non-idempotent call. Minor gaps remain around result ordering or pagination, but nothing critical is missing.

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 both query and limit (including the 1–25 range and default 8) are already fully documented in the schema. The description adds no syntax or formatting guidance beyond that, so the baseline 3 applies.

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 and resource (Threads keyword search), names the exact endpoint /v1/threads/search, and characterizes the corpus as short-form text/social posts. This clearly distinguishes it from siblings like search_reddit, search_posts, and search_tiktok.

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 purpose context (trend + voice research), which tells the agent when this tool is relevant. It does not, however, name alternatives or exclusion conditions against the many other search_* siblings, so routing still requires inference.

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