Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

List Bluesky profile posts

bluesky_profile_posts_list
Read-onlyIdempotent

List posts from a Bluesky profile by handle. Use it to review a user's recent activity, with cursor support for paginated results.

Instructions

List posts from a Bluesky profile by handle. Requires handle. Returns a list (use cursor when paginated).

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>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "bluesky_profile_posts_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
cursorNoPagination cursor returned by a previous response.
handleYesRequired. Bluesky handle whose posts should be listed.
userIdNoOptional Bluesky user id to speed up the request.
contextYesDescribe the user's underlying goal in one sentence, not the tool you are calling.
llm_modelYesThe exact model identifier you (the assistant) are running as, taken from your system prompt or environment (for example "claude-opus-4-8" or "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" and do not guess.
conversation_idNoEcho the conversation_id from the server's previous response. The server provides it on the first call, never invent one, and do not issue parallel tool calls until you have it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.2/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds two genuinely new behavioral facts: the return is a list, and pagination is handled via cursor. It says nothing about ordering, result caps, or what happens with a stale cursor.

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?

Three short sentences, front-loaded with the core action and resource, with no filler. The "Requires `handle`" clause is slightly redundant against the schema's required array, but the definition stays tight overall.

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 read-only list tool with 100% schema coverage and full annotation coverage of safety traits, the description supplies what remains: the target identity (handle), the return shape, and the pagination hook. Gaps around ordering and result volume are minor and not essential for correct invocation.

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 every parameter including cursor, userId, context, and conversation_id is documented in the schema itself. The description's only parameter remark, "Requires `handle`," merely restates the required list, adding no meaning beyond the schema. Baseline 3 applies when the schema does all the work.

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 names a specific verb and resource ("List posts") and scopes it to "a Bluesky profile by handle," which is clearly distinct from a profile-metadata tool like bluesky_profile_get. It stops short of explicitly contrasting itself with the many other posts-list siblings, so it is clear but not fully differentiated.

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?

The only guidance is "use cursor when paginated," which is a within-call mechanic rather than tool-selection advice. Nothing says when to choose this over bluesky_post_get or another network's posts list, and there are no stated prerequisites or exclusions.

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