Skip to main content
Glama

API Direct

by io.apidirect
OverviewDiscussionsAdmin

bluesky_user_likes

Get the posts a Bluesky user has liked, newest first. 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
Behavior3/5

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

With no annotations provided, the description carries the burden of disclosing behavior. It reveals ordering ('newest first') and cost ('Billed $0.003 per page'), and 'Get' implies a read operation. However, it does not mention authorization requirements, rate limits, or error behavior, leaving some behavioral gaps.

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 two concise sentences with no filler. It front-loads the main purpose, then adds billing and parameter constraint. 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?

The description covers the core purpose, output ordering, cost, and the key invocation constraint. The remaining parameter behaviors (pages, get_sentiment) are in the schema. Minor gaps like authentication or error handling do not prevent correct invocation.

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 parameter descriptions are already complete. The description adds a crucial constraint beyond the schema: 'Provide exactly one of username or url', which prevents invalid calls. This is meaningful semantic guidance.

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 uses a specific verb ('Get') and resource ('posts a Bluesky user has liked'), and adds ordering ('newest first'). It clearly distinguishes from sibling tools like bluesky_user_posts (posts by a user) and bluesky_post_likes (likes on a post) without needing to inspect schemas.

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?

The description gives clear context for when to use the tool: retrieving liked posts for a user. It does not explicitly name alternatives or exclusions, but the purpose is unambiguous enough for an agent to select it over 'bluesky_user_posts' or 'bluesky_post_likes'.

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