Crawlora MCP

threads_profile_reposts

Read-only

Fetch the first public Reposts-tab items for one Threads profile, preserving original authors and topic metadata. username accepts a profile handle; the logged-out tab has no cursor or sort filter, so check pagination_limited. Use threads_profile_media for media posts, threads_profile_posts for the cursor-paginated feed, or threads_profile_topics for tag discovery.

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_reposts"
  }
}

Input Schema

Name	Required	Description	Default
`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.

AddedOct 19, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful behavioral context beyond that: the logged-out tab 'has no cursor or sort filter, so check pagination_limited,' which tells the agent to expect a limited, non-paginated result. It does not mention auth or rate limits, but the pagination caveat is solid added value.

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 sentences, front-loaded with the primary action and scoping before the alternative-tool routing. It is dense but each sentence earns its place; slightly compressed phrasing but no wasted text.

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 an output schema present and annotations covering the read-only/open-world profile, the description need not explain return values. It covers the key limitation (no cursor/sort) and the sibling routing, making it complete enough for an agent to call correctly; only minor gaps remain.

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% and there is a single parameter already documented as 'Threads username.' The description adds only that it accepts a 'profile handle,' a marginal clarification. Baseline 3 is appropriate when the schema carries the parameter semantics.

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?

The description states a specific verb (Fetch) and resource (first public Reposts-tab items for one Threads profile), and explicitly names the sibling tools it is not (threads_profile_media, threads_profile_posts, threads_profile_topics). An agent can distinguish it from the other profile tools without opening any 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?

It gives explicit when-to-use routing: 'Use threads_profile_media for media posts, threads_profile_posts for the cursor-paginated feed, or threads_profile_topics for tag discovery.' The condition selecting each alternative is spelled out, leaving nothing to inference.

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?