Skip to main content
Glama

Bluesky account feed

bluesky_posts
Read-only

Bluesky Account Posts Feed: the latest public posts and replies of one Bluesky account (a handle such as name.bsky.social, a DID or a bsky.app profile URL), reposts left out. Per post the text, likes, replies, reposts, language, media links, time and URL in the shared social schema; next_cursor pages back through the feed. Bad input is free; not found or no match is not charged. Price: $0.01 per successful call, paid over x402 (USDC on Base); pass the payment in _meta["x402/payment"].

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": {
      "handle": "<handle>"
    },
    "name": "bluesky_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPosts per page, 1-25. Default 25.
cursorNonext_cursor of the previous page.
handleYesThe account: a Bluesky handle (a domain name such as name.bsky.social, or a bare name meaning name.bsky.social), a did:plc / did:web identifier, or a bsky.app profile URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  2. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations (which only declare read-only, open-world, non-idempotent). It discloses what is filtered out (reposts), the pagination mechanism (next_cursor pages back through the feed), the shape of each returned post, and full billing behavior including that bad input and no-match are free and payment is passed via _meta["x402/payment"].

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?

A single front-loaded sentence sequence that starts with the identity of the feed, then returns, then pagination, then pricing. Dense but almost every clause carries information; the pricing sentence is long but necessary for a paid endpoint.

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?

With no output schema, the description carries the return-value burden and does so by enumerating per-post fields (text, likes, replies, reposts, language, media links, time, URL) and the shared social schema. Combined with pagination and payment details, nothing an agent needs to call 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 the schema already documents limit, cursor and handle in detail. The description only restates the handle formats and the next_cursor semantics, adding no syntax or constraint detail the schema lacks — baseline 3 is correct.

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: 'the latest public posts and replies of one Bluesky account', with explicit scope exclusions ('reposts left out') and accepted identifier forms. An agent can tell this apart from bluesky_profile (profile metadata) and bluesky_search (keyword search) without opening either 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?

Usage is implied by the resource description: fetch a known account's timeline. There is no explicit when-to-use/when-not guidance and no named alternative (e.g. 'for keyword search use bluesky_search'), so the agent must infer the routing itself.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.