Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

threads_profile_replies

Retrieve public replies from a Threads profile’s Replies tab, preserving author and reply metadata. It returns the first public page and flags when pagination is limited.

Instructions

Retrieve public items from a Threads profile's Replies tab. Returns the first public page shown on a profile's Replies tab. Each item preserves its actual author and public reply metadata. The logged-out page has no continuation cursor; pagination_limited is true when Threads reports more items without a cursor or shows a login wall for additional items.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
usernameYesThreads username

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.13

TDQS

A3.5/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses useful behavioral traits: only the first public page is returned, the logged-out page has no continuation cursor, and a pagination_limited flag signals when more items exist without a cursor or behind a login wall. It also notes items preserve actual author and public reply metadata.

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?

The description is three sentences and front-loaded with the core purpose. The second sentence repeats the first's 'first public page' idea slightly, but overall it is efficient and every sentence contributes useful information about scope and pagination limits.

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 or annotations, the description adequately explains what is returned (public items with author and reply metadata) and a key behavioral constraint (pagination_limited). It omits finer details like the exact response shape or authentication requirements, but is complete enough for an agent to call the tool correctly.

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% with a single required 'username' parameter, so the schema already documents it. The description adds no parameter-specific meaning such as format hints (e.g., @ prefix, URL) or case sensitivity. Baseline 3 is appropriate.

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: 'Retrieve public items from a Threads profile's Replies tab.' The Replies tab scope inherently distinguishes it from sibling tools like threads_profile_posts, threads_profile_media, and threads_profile_reposts, though no explicit alternative is named.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives. The description explains the tool's behavior but does not state conditions, exclusions, or which sibling to prefer for other profile tabs. Usage is only implied by the tool name and scope.

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