Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

threads_profile_replies

Read-only

Fetch the first logged-out public Replies-tab items for one Threads profile, retaining each actual author and reply relationship. username accepts a profile handle; no public cursor or sort/filter is available, so check pagination_limited. Use threads_post_replies for one post's replies, threads_profile_posts for the cursor-paginated Threads tab, or threads_profile_media for media.

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

Input Schema

NameRequiredDescriptionDefault
usernameYesThreads username.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, but the description adds real behavioral context: results are logged-out (no auth), limited to the first page, and there is no public cursor or sort/filter so pagination_limited should be checked. It also notes that each actual author and reply relationship is retained, hinting at data shape. It stops short of describing rate limits or the response envelope, which the output schema likely covers.

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?

Front-loaded with the core purpose, then the parameter note, then alternatives. Dense but every clause earns its place. Slightly packed into three long sentences, but no wasted 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?

For a single-parameter read tool with an output schema, the description covers the important operational facts: no auth needed, first-page-only retrieval, no cursor/sort/filter, and which siblings to prefer. Return-value details are correctly left to the output schema.

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% for the single username parameter, so the schema already documents it. The description adds only a minor clarification that username accepts a profile handle. Baseline 3 is appropriate 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?

States a specific verb (Fetch), resource (Replies-tab items for one Threads profile), and scope (first logged-out public items). It explicitly differentiates from the sibling tools threads_post_replies, threads_profile_posts, and threads_profile_media, so an agent can route correctly 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?

Names three alternatives and the condition that selects each: threads_post_replies for a single post, threads_profile_posts for the cursor-paginated Threads tab, threads_profile_media for media. It also tells the agent to check pagination_limited, giving explicit usage context.

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

All Crawlora MCP toolsInspect
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