Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

threads_profile_posts

Fetch public posts from a Threads profile by username, including text, media URLs, engagement counts, and a cursor for paging through more posts. Use the cursor to fetch more pages when available.

Instructions

Retrieve public posts from a Threads profile. Lists public posts from the profile's Threads tab by username. Each item has its code, URL, text, creation time, image and video URLs, like, reply, repost and quote counts, reply flag and author. When has_more is true, pass next_cursor unchanged as cursor to fetch the next page; pagination_limited is true if Threads withholds a usable cursor.

Input Schema

NameRequiredDescriptionDefault
cursorNoOpaque cursor returned by the previous response
usernameYesThreads username

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/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 it does substantial work: it enumerates the returned fields and documents pagination mechanics (has_more, next_cursor round-trip, pagination_limited when Threads withholds a cursor). It omits auth/rate-limit behavior, but for a public read tool this is above the bar.

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?

Purpose is front-loaded, followed by item shape and then pagination rules, so the reader can stop early if needed. The long field enumeration is dense but justified given the absence of an output schema; nothing is padding.

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?

For a 2-parameter read tool with no annotations and no output schema, the description covers purpose, return shape, and pagination quirks, which is what an agent needs to call it correctly. Deeper operational details (auth, rate limits) are the only real gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains that cursor takes the previous response's next_cursor unchanged and is only needed when has_more is true. That linkage is not in the schema and improves the odds of correct invocation.

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 posts from a Threads profile') and pins the scope to the profile's Threads tab, which implicitly separates it from the sibling media/replies/reposts tabs. It does not explicitly name those siblings, but the resource is unambiguous.

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 'by username' scoping and the Threads-tab limitation imply when to use it, but there is no explicit when-to-use vs alternatives (e.g. threads_post, threads_search, threads_profile_replies) and no stated prerequisites. Pagination steps are given, but selection guidance is left to inference.

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