Skip to main content
Glama

bluesky_profile

Look up a public Bluesky profile by handle or DID to retrieve bio, follower counts, labels, and recent posts with engagement metrics for OSINT account research.

Instructions

Look up a public Bluesky profile and recent posts (keyless AT Protocol API).

actor accepts a handle (bsky.app) or a DID. Returns bio, counts, labels and recent original posts/reposts with engagement counts.

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": {
      "actor": "<actor>"
    },
    "name": "bluesky_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
actorYes
postsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and delivers the key facts: the API is keyless (no credential or auth step needed) and the response shape includes bio, counts, labels, and recent original posts/reposts with engagement counts. It stops short of disclosing rate limits, pagination behavior, or what happens for nonexistent/protected accounts, which keeps it below a 5.

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?

Three short sentences, zero filler, with the core purpose front-loaded and input format detail immediately after. The trailing sentence on return contents is compact and 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?

For a two-parameter read tool with no output schema and no annotations, the description covers purpose, input formats, and return contents adequately, so an agent could call it correctly. The remaining gap is the undocumented `posts` limit and unspecified error behavior for missing profiles.

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 0%, so the description must compensate. It does explain the critical `actor` parameter's accepted formats (bsky.app handle or DID), which is genuinely useful, but the `posts` parameter is never mentioned — its meaning and the default of 10 come only from the schema's title and default field.

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 opens with a specific verb and resource: 'Look up a public Bluesky profile and recent posts.' It adds the data source (keyless AT Protocol API) and scopes the resource to public profiles, so an agent can identify the operation without inspecting the schema, and no sibling tool in the list targets Bluesky profiles.

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 only implied: the word 'public' signals that private or suspended accounts are out of scope, but there is no explicit statement of when to prefer this over alternatives and no named alternative. With no comparable sibling, the omission is low-impact, but the guidance is inferential rather than stated.

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