Skip to main content
Glama
Fetchproof MCP Server

Fetchproof MCP Server

bluesky_user_posts

Fetch Bluesky user posts by handle or user ID; use the user ID for faster responses. This retrieves public post data via the Fetchproof API.

Instructions

bluesky: Posts. GET /v1/bluesky/user/posts. Provide one of: handle, user_id. Get Bluesky user posts. Use user_id for faster response times. Costs 1 credit when it succeeds. Errors, blocked or timed-out requests, invalid requests and cache hits cost nothing. A not-found or empty result is charged only where that operation's published cost says so.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bluesky_user_posts"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleNoBluesky handle
user_idNoBluesky user DID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description does carry real behavioral weight: it discloses the credit cost on success, that errors/cache hits/timeouts are free, and that not-found/empty results are billed per the operation's published cost. That is useful beyond structured fields, but it says nothing about read-only nature, pagination, result caps, or rate limiting for a list endpoint.

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

Conciseness3/5

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

The core purpose and parameter rule are front-loaded and easy to scan, but the three-sentence billing paragraph is verbose for what amounts to "successful calls cost 1 credit, failures and cache hits are free." Some of that text is boilerplate that crowds out more useful facts such as pagination behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with no output schema, the essentials are present, and return values need not be described. However, the description never addresses pagination, result limits, or what happens when both identifiers are omitted, which are the remaining questions an agent would have before calling it.

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 would be 3, but the description adds meaning the schema does not encode: the schema marks no parameters required and has no oneOf constraint, while the description states exactly one of handle/user_id must be supplied. It also explains the performance tradeoff favoring user_id, which the schema's DID label alone does not convey.

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 uses a specific verb and resource ("Get Bluesky user posts") and includes the underlying endpoint, which separates it from bluesky_post (single post) and bluesky_profile. It stops short of explicitly naming a sibling or scope limits (e.g. how many posts, whose timeline), so it is clear but not maximally differentiated.

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?

It states a selection rule between the two identifier parameters ("Provide one of: handle, user_id") and a preference ("Use user_id for faster response times"), which is genuine invocation guidance. It gives no guidance on when to choose this tool over the other-platform *_user_posts siblings or when it is inappropriate, so usage context is only implied.

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