Skip to main content
Glama
exileum

meta-mcp

threads_search_posts

Search public Threads posts by keyword or topic tag. Filter results by date, media type, author, and ordering to find relevant content.

Instructions

Search for public Threads posts by keyword or topic tag. Requires threads_keyword_search permission.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch keyword or query
search_typeNoResult ordering: TOP (default) or RECENT
search_modeNoSearch by KEYWORD (default) or TAG
media_typeNoFilter results by media type
author_usernameNoFilter results by author username
sinceNoStart date (Unix timestamp)
untilNoEnd date (Unix timestamp)
limitNoNumber of results (max 100, default 25)
afterNoPagination cursor
Behavior2/5

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

No annotations are present, so the description must provide behavioral context. It mentions the required permission but omits other traits such as rate limits, pagination behavior, or that results are public. The description is too minimal to adequately convey behavioral traits.

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?

Single, concise sentence that front-loads the purpose. No wasted words, but it may be too brief for the tool's complexity. Still, it is efficient and to the point.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 9 parameters (including enums and pagination cursor) and no output schema, the description lacks context about ordering, filtering, pagination, and result structure. It is not complete enough for an agent to understand how to effectively use the tool.

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?

All parameters have schema descriptions (100% coverage), so the description adds no new information beyond 'by keyword or topic tag', which partially explains q and search_mode. 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?

Clearly states the action (search), the resource (public Threads posts), and the method (by keyword or topic tag). Mentions required permission. Distinguishes from sibling tools like threads_get_posts which retrieves specific posts.

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

Usage Guidelines2/5

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

Only notes a permission requirement but provides no guidance on when to use this tool vs. alternatives (e.g., threads_get_mentions, threads_get_posts). Does not specify when not to use it.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/exileum/meta-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server