Skip to main content
Glama

API Direct

by io.apidirect
OverviewDiscussionsAdmin

bluesky_user_posts

Get a user's feed by handle: their posts, replies, and reposts in feed order (the pinned post first, then newest first), each flagged with is_reply, is_repost, and is_pinned. Billed $0.003 per page. Provide exactly one of username or url.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlNoBluesky profile URL, e.g. https://bsky.app/profile/bsky.app (max 500 characters).
pagesNoNumber of pages to fetch, 1-20 (default: 1). Each page returns up to 50 posts; you are billed per page returned.
usernameNoBluesky handle, e.g. bsky.app, with or without leading @, or the account's DID (max 100 characters).
get_sentimentNoAdd AI sentiment analysis (Plutchik emotions, dominant_emotion, intensity, and positive/negative/neutral polarity) to each result. Adds a small surcharge per page, or per request on single-request endpoints.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / url / description
      Previous value: -"Bluesky profile URL, e.g. https://bsky.app/profile/bsky.app (max 500 characters). Provide either username or url."New value: +"Bluesky profile URL, e.g. https://bsky.app/profile/bsky.app (max 500 characters)."
    • changedInput schema / properties / username / description
      Previous value: -"Bluesky handle, e.g. bsky.app, with or without leading @, or the account's DID (max 100 characters). Provide either username or url."New value: +"Bluesky handle, e.g. bsky.app, with or without leading @, or the account's DID (max 100 characters)."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the feed ordering, flags, billing per page, and the input constraint. It does not mention error cases, rate limits, or authentication, but for a read-only tool these are minor. It adds useful behavioral context beyond the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, densely packed sentence that front-loads the purpose and includes key flags and billing. No wasted words; every part earns its place.

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 no output schema, the description conveys the output content (posts, replies, reposts with flags) adequately. It misses potential error behavior or what happens when both username and url are provided, but for a simple feed tool it is largely complete.

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 parameters are well documented. The description adds the essential 'exactly one of username or url' rule, which is not captured in the schema, and clarifies billing implications for pages. This adds meaningful value beyond the schema.

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?

The description clearly states the verb ('Get'), the resource ('a user's feed by handle'), and the specific content ('posts, replies, and reposts' with flags). It distinguishes itself from siblings like bluesky_user_profile (profile info) and post-specific tools by focusing on the feed.

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 gives a critical usage constraint ('Provide exactly one of username or url') and mentions billing per page, but it does not explicitly name alternatives or specify when to use this tool over siblings. The context is clear, but no exclusions are stated.

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

All API Direct 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