Skip to main content
Glama
Sign In

API Direct

by io.apidirect
OverviewDiscussionsAdmin

Threads User Posts

threads_user_posts
Read-only

Get a Threads (Meta) user's recent posts by username, newest first. Returns post text, engagement metrics, media, link previews, timestamps, permalinks, whether each post is pinned and Threads' AI label (ai_label). Up to about 35 posts per page. Billed $0.006 per page.

Input Schema

NameRequiredDescriptionDefault
pagesNoNumber of pages to fetch, 1-60 (default: 1). Each page returns up to about 35 posts
usernameYesThreads username, with or without leading @ (max 100 characters)
get_sentimentNoAdd AI sentiment analysis (Plutchik emotions, dominant_emotion, intensity, and positive/negative/neutral polarity) to each result. Adds a small surcharge per page, or per request on single-request endpoints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / pages
      Added value: +{
+  "default": 1,
+  "description": "Number of pages to fetch, 1-60 (default: 1). Each page returns up to about 35 posts",
+  "type": "integer"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / get_sentiment / description
      Previous value: -"Add AI sentiment analysis (Plutchik emotions, dominant_emotion, intensity, and positive/negative/neutral polarity) to each result. Adds a small per-page surcharge."New value: +"Add AI sentiment analysis (Plutchik emotions, dominant_emotion, intensity, and positive/negative/neutral polarity) to each result. Adds a small surcharge per page, or per request on single-request endpoints."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the read-only/non-destructive/open-world profile, and the description adds genuinely useful context beyond them: pagination size (~35 per page) and per-page cost ($0.006). It omits failure behavior for private, suspended, or nonexistent accounts, which is the main remaining gap for an open-world read.

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?

Three sentences, each carrying distinct information: what it returns, how results are shaped (ordering, page size), and price. Ordering and cost are front-loaded where an agent will see them before deciding to call.

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 (text, engagement, media, link previews, timestamps, permalinks, pinned, ai_label), so an agent knows what it gets. It lacks only edge-case behavior for missing or private users and whether ai_label can be null.

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 coverage is 100%, including the 1-60 page range and the get_sentiment surcharge note, so the baseline of 3 applies. The description only restates the page size already documented in the schema and adds no new meaning about parameter interaction.

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 ('Get a Threads (Meta) user's recent posts by username') plus ordering ('newest first'), which cleanly separates it from threads_user_profile and search_threads. It never names an alternative explicitly, so it stops just short of full sibling routing.

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?

Usage is implied by the purpose (pull a known user's timeline), but the description never says when to prefer this over search_threads (keyword discovery) or threads_user_profile (account metadata), nor does it state prerequisites like the account being public or existing.

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

All API Direct toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources