Skip to main content
Glama
Threads Profile and Posts MCP Server

Threads Profile and Posts MCP Server

Get Threads profiles and posts

get_threads_profiles
Read-onlyIdempotent

Fetch public Threads profile data and recent posts as a logged-out visitor, including follower counts, bios, bio links, verification status, engagement metrics, and media links.

Instructions

Read public Threads profiles the way a logged out visitor sees them. Returns one row per profile with username, name, verified mark, follower count, bio, bio links, and profile photo, plus one row per post the profile page shows (the newest threads and the author's continuation posts) with text, date, likes, replies, reposts, quotes, and media links.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_threads_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
profilesNoThreads usernames (zuck or @zuck) or profile links (https://www.threads.com/@zuck, threads.net links work too). A post link is read as its author's profile. In Clay, wrap a column in a one item list.
include_postsNoyes (default): one row per post the profile page shows to a logged out visitor, the newest threads with the author's own continuation posts. no: profile rows only.
max_charge_usdNoOptional. The run stops before a charge that would pass this amount. Free rows are always returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, openWorld, idempotent and non-destructive, so the safety bar is low. The description still adds real value by disclosing the data-visibility boundary (public, logged-out view only) and the output shape of one row per profile plus one row per post, which matters given there is no output schema. Pagination and rate-limit behavior are left unstated.

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?

Two sentences, front-loaded with the core action and scope, then the field inventory. It is dense and slightly run-on in the second sentence but no sentence is wasted.

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?

With no output schema, the description carries the return-value burden itself and does so thoroughly, listing profile fields and post fields. Parameter documentation is fully covered by the schema, so nothing an agent needs to call this correctly 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 all three parameters (profiles, include_posts, max_charge_usd) are already documented in the schema. The description merely echoes the post-row behavior of include_posts and adds no new meaning about input formats or the cost cap. 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 ("Read public Threads profiles") and pins the scope with a concrete qualifier: "the way a logged out visitor sees them." It then enumerates the returned fields, so an agent knows exactly what data it gets without opening anything else.

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 logged-out framing implies this is for public-profile lookups and nothing else, but there is no explicit when-to-use or when-not guidance and no alternatives are named (none exist among siblings). Usage is inferable rather than stated.

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