Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

threads_profile_reposts

Retrieve public posts reposted by a Threads profile and return the first page from its Reposts tab, preserving original authors and metadata, with a flag when pagination is limited.

Instructions

Retrieve public posts reposted by a Threads profile. Returns the first public page shown on a profile's Reposts tab. Each item preserves the original post author and metadata. pagination_limited is true when Threads gates more items behind login or reports more items without a supported cursor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesThreads username

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.13

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that only the first public page is returned and explains the `pagination_limited` flag semantics (login gating or missing cursor). It stops short of stating read-only intent or any account-visibility constraints explicitly, but 'Retrieve public' covers much of that.

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?

Four short sentences, well front-loaded with the core action and return scope, and the pagination caveat placed last. Every sentence carries information, though the metadata/pagination sentences could be marginally tighter.

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?

No output schema exists, so the description must convey return values, and it does: first public page, preserved original author/metadata, and the `pagination_limited` flag. What it omits is why no cursor parameter exists despite discussing pagination, but overall it is sufficient for correct invocation.

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?

Only one parameter (username) with 100% schema description coverage, so the schema already defines it as the Threads username. The description adds no format or syntax detail beyond that, making the baseline 3 appropriate.

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 ('Retrieve public posts reposted by a Threads profile') and clearly scopes it to the Reposts tab. This distinguishes it from sibling tools like threads_profile_posts, threads_profile_replies, and threads_profile_media without requiring 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 Guidelines3/5

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

The description implies usage (fetching a profile's repost feed) but never states when to choose this over threads_profile_posts or threads_profile_replies, nor any prerequisites about the target account. The distinction is left to inference from the word 'reposted.'

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