Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Threads profile posts

threads_profile_posts_list
Read-onlyIdempotent

Fetch posts from a Threads profile by handle to review recent activity; optionally return a trimmed response with fewer post fields.

Instructions

List posts from a Threads profile by handle. Requires handle. 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": {
      "handle": "<handle>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "threads_profile_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
trimNoWhen true, returns a smaller response with fewer post fields when available.
handleYesRequired. Threads handle whose posts should be listed.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
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.
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety and mutability are covered. The description adds only 'Returns a list', which conveys little about pagination, result volume, or the trim-related response variance documented in the schema. With annotations carrying the safety burden, this is an adequate but thin addition.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the purpose, which is good. However, 'Requires `handle`' duplicates the schema's required field and 'Returns a list' is near-tautological, so two of the three sentences add little value.

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?

For a simple read-only list tool whose five parameters are fully documented in the schema and whose safety profile is fully declared in annotations, the description covers the essential purpose and scope. The missing pieces (pagination, returned fields) are minor given there is no output schema, though 'Returns a list' is the only return hint provided.

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 handle, trim, context, llm_model, and conversation_id are all documented in the schema itself. The description merely restates that handle is required and adds no format, syntax, or edge-case meaning beyond the schema. Baseline 3 is appropriate.

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: 'List posts from a Threads profile by handle.' The scoping to a profile-by-handle distinguishes it conceptually from a search-style sibling, though it never names an alternative. Clear but not explicitly differentiated from siblings like threads_profile_get.

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?

No when-to-use or when-not-to-use guidance at all. It does not say when to pick this over threads_profile_get or any of the many other *_profile_posts_list siblings. The 'by handle' phrasing implies usage but does not guide selection.

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