Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Search Threads posts

threads_search_list
Read-onlyIdempotent

Search public Threads posts by keyword and optional date range, returning a list of matching posts for research or monitoring.

Instructions

Search Threads posts by keyword. Requires query. Returns a list.

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": {
      "query": "<query>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "threads_search_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoWhether to request a smaller response shape when available.
queryYesRequired. Search query text for public Threads posts.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
endDateNoOptional end date filter in YYYY-MM-DD format.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
startDateNoOptional start date filter in YYYY-MM-DD format.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true and destructiveHint=false, so safety and openness are covered without the description. The description adds only "Returns a list", omitting anything about result volume, ranking, or that a conversation_id handshake is expected before parallel calls, which is the one non-obvious behavior of this tool.

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 short sentences, front-loaded with the action, with no filler or hedging. The third sentence ("Returns a list") and the "Requires `query`" restatement are near-redundant with structured data, keeping it short of a 5.

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

Completeness3/5

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

For a seven-parameter search tool with three required fields, including analytics-only and sequencing parameters, the description says nothing beyond the bare action; the schema carries that load at 100% coverage and there is no output schema to explain. It is minimally complete but leaves the required-parameter ritual and result shape entirely to structured fields.

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 seven parameters, including the required context, llm_model and conversation_id fields, are documented in the schema itself. The description repeats "Requires `query`" without adding format, syntax or interaction guidance, so baseline 3 applies.

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 and resource ("Search Threads posts") plus the retrieval mode ("by keyword"), which separates it from the profile-scoped listing siblings such as threads_profile_posts_list. It does not name any sibling explicitly, so discrimination relies on the agent inferring keyword-vs-profile semantics.

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?

There is no when-to-use or when-not-to-use guidance and no named alternative, despite many siblings covering adjacent post-retrieval cases (threads_users_search, threads_profile_posts_list, threads_post_get). The agent must infer from the tool name that this is the keyword-search path rather than a profile browse.

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