Skip to main content
Glama
Sign In
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

bluesky_author_feed

Fetch a Bluesky account's posts newest first, with text, engagement counts, and attached images, link cards, or quoted posts; supports pagination by cursor.

Instructions

A Bluesky account's posts. Returns a page of a Bluesky account's posts, newest first, including text, engagement counts, and any attached images/link card/quoted post.

Input Schema

NameRequiredDescriptionDefault
actorYesA handle (e.g. bsky.app) or DID
limitNoPage size, 1-100
cursorNoPagination cursor from a previous response's cursor field

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose useful traits: pagination ('a page'), ordering ('newest first'), and returned content (text, engagement counts, images/link card/quoted post). It omits auth/permission needs and rate limits, so it is adequate but incomplete.

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?

Two sentences, front-loaded and waste-free overall. There is mild redundancy between the fragment 'A Bluesky account's posts' and the following sentence that repeats the same idea, but it remains compact.

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 simple read/feed tool with a fully documented 3-param schema and no output schema, the description covers the essentials including return contents and ordering. It could add auth context, but nothing critical to calling it correctly is missing.

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 actor, limit, and cursor are already fully documented in the schema. The description adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

The description clearly states the resource (a Bluesky account's posts) and the action (returns a page of them, newest first). An agent can tell it fetches a specific account's feed. However, it does not distinguish itself from sibling feed-like tools such as bluesky_posts or bluesky_post_quotes, so it stops short of a 5.

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?

There is no when-to-use guidance, no conditions for selecting this tool over alternatives, and no named siblings despite many bluesky_* siblings. The agent must infer usage entirely.

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