Skip to main content
Glama
berlinbra

BlueSky MCP Server

bluesky_get_profile

Retrieve user profile information from the BlueSky social network using its official API with authentication and error handling.

Instructions

Get a user's profile information

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Executes the bluesky_get_profile tool by calling the Bluesky API's get_profile endpoint for the server's configured account identifier.
    if name == "bluesky_get_profile":
        response = await asyncio.to_thread(
            bluesky.client.app.bsky.actor.get_profile,
            {'actor': IDENTIFIER}
        )
  • Registers the bluesky_get_profile tool with its name, description, and input schema (no required parameters).
        name="bluesky_get_profile",
        description="Get a user's profile information",
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
    types.Tool(
  • Defines the input schema for bluesky_get_profile: an empty object (no parameters expected).
        name="bluesky_get_profile",
        description="Get a user's profile information",
        inputSchema={
            "type": "object",
            "properties": {},
        },
    ),
    types.Tool(
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'Get[s] a user's profile information', implying a read-only operation, but doesn't clarify how the user is identified (e.g., by handle, DID, or other means), whether authentication is required, rate limits, or what specific information is returned. This leaves significant gaps for a tool with zero annotation coverage.

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, clear sentence with zero waste—it directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy for an agent to parse quickly.

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

Completeness2/5

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

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimal but inadequate. It doesn't explain how the user is specified (e.g., via context or implicit means), what profile information is returned, or any behavioral traits like authentication needs. For a tool with no structured data to rely on, the description should provide more context to be 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?

The input schema has 0 parameters with 100% description coverage, so the schema fully documents the lack of inputs. The description doesn't add parameter details beyond this, but since there are no parameters to explain, it doesn't need to compensate. A baseline of 4 is appropriate as the description is sufficient given the empty parameter set.

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 clearly states the tool's purpose with a specific verb ('Get') and resource ('a user's profile information'), making it immediately understandable. However, it doesn't differentiate this tool from potential sibling tools that might also retrieve profile data, such as 'bluesky_search_profiles', which prevents a perfect score.

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 description provides no guidance on when to use this tool versus alternatives like 'bluesky_search_profiles' or other sibling tools. It lacks any mention of prerequisites, context, or exclusions, leaving the agent to infer usage based on the tool name alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/berlinbra/BlueSky-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server