Crawlora MCP

bluesky_post_thread

Read-only

Returns a Bluesky post along with its nested replies (and, when the post is itself a reply, its parent chain), up to depth levels deep. Public data, sourced from the AT Protocol's public, credential-free AppView API. uri: The post's at:// URI, e.g. from an author-feed or search-actors result's post uri field. Use bluesky_posts to retrieve look up Bluesky posts in a batch.

Input Schema

Name	Required	Description	Default
`uri`	Yes	The post's at:// URI, e.g. from an author-feed or search-actors result's post uri field
`depth`	No	Reply-tree depth, 1-10

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.

Changed2 schema fields changedOct 7, 2026

addedInput schema / properties / depth / description
```
Added value: +"Reply-tree depth, 1-10"
```

addedInput schema / properties / uri / description

Added value: +"The post's at:// URI, e.g. from an author-feed or search-actors result's post uri field"

First observedOct 7, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Adds meaningful behavior beyond the readOnlyHint/openWorldHint annotations: the parent-chain expansion for reply posts, the depth-bounded nesting, and the fact that the source is a credential-free public AppView API (no auth needed). It doesn't discuss ordering or pagination of replies, which keeps it from a 5.

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-loads the primary behavior (what is returned) then covers the parent chain, data provenance, and the sibling pointer. Slightly dense in the middle but no wasted sentences.

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?

Given 2 params, an output schema present (so return shape need not be described), and annotations covering safety, the description supplies the missing behavioral context (parent chain, public API). Minor gap: no guidance on reply ordering or what 'depth' bounds exactly.

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%, so the schema already documents both 'uri' and 'depth' (1-10). The description echoes the uri example and the depth semantics but adds no new syntax or edge-case information, so the baseline of 3 applies.

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: returns a Bluesky post with its nested replies and, when the post is itself a reply, its parent chain. This distinguishes it from sibling bluesky_posts (batch lookup) and bluesky_post_likes/quotes/reposted_by (related entity lists).

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

Usage Guidelines4/5

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

Explicitly points to bluesky_posts for batch lookups, giving a clear alternative. It also describes the parent-chain behavior, which implicitly tells the agent when the tool is useful. No explicit when-not-to-use case beyond the batch pointer.

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.