Skip to main content
Glama
Social Fetch MCP

Social Fetch MCP

Official

Get Bluesky profile

bluesky_profile_get
Read-onlyIdempotent

Fetch a Bluesky profile by handle to look up creators or accounts and access public profile details for research, verification, or outreach.

Instructions

Get a Bluesky profile for a creator or account. Requires handle.

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_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesRequired. Bluesky handle to look up, with or without a leading @.
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

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered without the description. The description adds nothing beyond that – no mention of error behavior for unknown handles, rate limits, or what a profile lookup returns.

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?

Two short sentences, front-loaded with the action and resource. The second sentence is largely redundant with the schema's required-field declaration, which keeps it from a 5, but there is no padding or digression.

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?

This is a simple read-only lookup with full schema coverage and complete annotations, so the description is technically sufficient to invoke it. However, it gives no hint of what the response contains (fields, error on unknown handle), which would be the remaining value-add for a profile-fetch tool.

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 the schema already documents handle (including the optional leading @), context, llm_model and conversation_id in detail. The description merely restates that handle is required, adding no meaning beyond the schema, which is the baseline-3 case.

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?

States a specific verb and resource ('Get a Bluesky profile') and names the target object ('a creator or account'), which distinguishes it from the many other platform profile tools by platform name. It does not explicitly distinguish itself from its closest sibling, bluesky_profile_posts_list, but the resource noun does that implicitly.

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 usage statement is 'Requires `handle`', which is a parameter prerequisite rather than when-to-use guidance. Nothing tells the agent when to pick this over bluesky_profile_posts_list or bluesky_post_get, nor what conditions make a profile lookup appropriate.

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