Skip to main content
Glama

get_profile

Retrieve user profile information from Bluesky Social, including authenticated user or specified handle data.

Instructions

Get a user profile.

Args:
    ctx: MCP context
    handle: Optional handle to get profile for. If None, gets the authenticated user

Returns:
    Profile data

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
handleNo

Implementation Reference

  • The @mcp.tool()-decorated function that implements the core logic for retrieving a Bluesky user profile, handling optional handle parameter and authentication.
    @mcp.tool()
    def get_profile(ctx: Context, handle: Optional[str] = None) -> Dict:
        """Get a user profile.
    
        Args:
            ctx: MCP context
            handle: Optional handle to get profile for. If None, gets the authenticated user
    
        Returns:
            Profile data
        """
        try:
            bluesky_client = get_authenticated_client(ctx)
    
            # If no handle provided, get authenticated user's profile
            if not handle:
                handle = bluesky_client.me.handle
    
            profile_response = bluesky_client.get_profile(handle)
            profile = profile_response.dict()
            return {"status": "success", "profile": profile}
        except Exception as e:
            error_msg = f"Failed to get profile: {str(e)}"
            return {"status": "error", "message": error_msg}
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 mentions the authenticated user fallback, which is useful, but doesn't cover other important aspects like authentication requirements, rate limits, error conditions, or what 'Profile data' includes. For a read operation with zero annotation coverage, this leaves significant 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 efficiently structured with a clear purpose statement followed by Args and Returns sections. Every sentence adds value without redundancy, making it easy to scan and understand quickly.

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?

Given the tool's moderate complexity (single optional parameter, read operation), no annotations, and no output schema, the description is minimally adequate. It covers the basic purpose and parameter behavior but lacks details on authentication, error handling, and the structure of returned 'Profile data', which would be helpful for an AI agent.

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 description adds meaningful context for the single parameter ('handle') by explaining its optional nature and the behavior when it's None (gets authenticated user's profile). With 0% schema description coverage and only one parameter, this adequately compensates, though it could specify what format the handle should be in.

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 ('user profile'), making it immediately understandable. However, it doesn't explicitly differentiate this from sibling tools like 'resolve_handle' or 'check_auth_status', which might also retrieve user-related information.

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?

The description provides implied usage guidance by explaining that if no handle is provided, it gets the authenticated user's profile. However, it doesn't explicitly state when to use this tool versus alternatives like 'resolve_handle' or 'get_followers', nor does it mention any prerequisites or exclusions.

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/gwbischof/bluesky-social-mcp'

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