Crawlora MCP

threads_profile_posts

Read-only

Fetch cursor-paginated public post items from a Threads profile's Threads tab, including media and topic fields. username is a profile handle and cursor is the prior next_cursor. If has_more is true without a cursor, check pagination_limited. Use threads_profile for profile counts, threads_post for one post, threads_search to find posts, or threads_profile_replies, threads_profile_media, and threads_profile_reposts for the other tabs.

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": {
      "username": "<username>"
    },
    "name": "threads_profile_posts"
  }
}

Input Schema

Name	Required	Description	Default
`cursor`	No	Opaque cursor from a previous profile-posts response.
`username`	Yes	Threads username.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=true), and the description adds pagination behavior beyond them: cursor is the prior next_cursor and the has_more-without-cursor edge case pointing to pagination_limited. It does not discuss auth or rate limits, but for a read-only public endpoint the added pagination semantics are solid.

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?

Purpose and scope are front-loaded, followed by parameter clarification and routing. Every sentence carries information (chaining semantics, edge case, sibling routing) with no filler.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. The description supplies the pagination chaining rule and the has_more/pagination_limited edge case, leaving nothing an agent needs before calling.

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% with only two params, so the schema documents them fully; description adds marginal value by framing username as a profile handle and cursor as the prior response's next_cursor. This matches the baseline-3 expectation when the schema does the heavy lifting.

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?

Starts with a specific verb and resource ('Fetch cursor-paginated public post items from a Threads profile's Threads tab') plus the scope of fields (media, topic). It explicitly distinguishes itself from sibling tabs, so an agent can identify it without opening the schema.

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

Usage Guidelines5/5

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

Names concrete alternatives and the conditions that select them: threads_profile for counts, threads_post for one post, threads_search to find posts, and the replies/media/reposts tools for other tabs. This is explicit when/when-not routing.

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

All Crawlora MCP tools Inspect

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

Need Help?