Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bluesky_post_quotes

Fetch posts quoting a Bluesky post by its at:// URI, and page through results with limit and cursor for engagement details.

Instructions

List quotes of a Bluesky post. Lists the Bluesky posts that quote a given post, identified by its at:// post uri, which is required. limit defaults to 25 and is capped at 100; pass the returned cursor back for the next page. Each post has its text, author, created_at, langs, like, quote, reply and repost counts, images and external link card.

Input Schema

NameRequiredDescriptionDefault
uriYesThe quoted post's at:// URI
limitNoPage size, 1-100
cursorNoPagination cursor

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.5

TDQS

A4.1/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 disclose real behavior: default limit 25, cap of 100, and cursor-based pagination. It also enumerates the fields present on each returned post (text, author, created_at, engagement counts, images, external card), which serves as a return-value contract in the absence of an output schema.

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 core purpose is front-loaded and the remaining sentences cover pagination and return shape efficiently. Minor redundancy between the first two sentences ('List quotes' then 'Lists the Bluesky posts that quote'), but no wasted 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 paginated read tool with no annotations and no output schema, the description supplies the essentials: how to identify the post, page-size behavior, cursor handling, and the shape of returned items. Only alternative-tool routing and auth/permission notes are missing, which are secondary for a public read.

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 meaning beyond the schema: it gives the limit default of 25 (schema only says 'Page size, 1-100') and explains that the returned cursor should be passed back for the next page. That is genuine added value over the structured fields.

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 ('List quotes of a Bluesky post') and immediately defines it as 'the Bluesky posts that quote a given post'. This clearly distinguishes it from siblings like bluesky_post_likes and bluesky_post_reposted_by 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 Guidelines3/5

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

The description establishes the required context (must supply the post's at:// uri) and explains pagination, but never names the adjacent alternatives (bluesky_post_likes, bluesky_post_reposted_by) or says when to prefer this over them. Usage is implied rather than routed.

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