AT Protocol MCP Server

get_user_profile

Read-only

Retrieve a user profile from AT Protocol to get handle, display name, bio, avatar, and follower counts. Works without authentication for public data, and with authentication for viewer-specific details.

Instructions

Retrieve a user profile from AT Protocol, returning handle, display name, bio, avatar, banner, follower/following/post counts, and applied labels. Works without authentication; richer with auth — authenticated calls also return viewer-specific fields (following, followedBy, muted, blocking, blockedBy). Use get_user_summary for a condensed overview or get_user_connections for follower/following lists. Subject to per-tool rate limiting.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`actor`	Yes	Handle (e.g. alice.bsky.social) or DID (e.g. did:plc:...) of the account whose profile to retrieve.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`success`	Yes	Whether the profile was retrieved successfully.
`profile`	Yes	Full profile record for the requested account.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.6.2Jun 23, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```

Changed2 schema fields changedv0.6.0Jun 11, 2026

addedInput schema / properties / actor / description

Added value: +"Handle (e.g. alice.bsky.social) or DID (e.g. did:plc:...) of the account whose profile to retrieve."

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "profile": {
+      "description": "Full profile record for the requested account.",
+      "properties": {
+        "avatar": {
+          "description": "URL of the account avatar image, if set.",
+          "type": "string"
+        },
+        "banner": {
+          "description": "URL of the profile banner image, if set.",
+          "type": "string"
+        },
+        "description": {
+          "description": "Bio/description text set by the user, if any.",
+          "type": "string"
+        },
+        "did": {
+          "description": "Decentralized identifier (DID) of the account.",
+          "type": "string"
+        },
+        "displayName": {
+          "description": "Display name set by the user, if any.",
+          "type": "string"
+        },
+        "followersCount": {
+          "description": "Number of accounts following this user.",
+          "type": "number"
+        },
+        "followsCount": {
+          "description": "Number of accounts this user follows.",
+          "type": "number"
+        },
+        "handle": {
+          "description": "Human-readable handle of the account (e.g. alice.bsky.social).",
+          "type": "string"
+        },
+        "indexedAt": {
+          "description": "ISO 8601 timestamp of when this profile was last indexed.",
+          "type": "string"
+        },
+        "labels": {
+          "description": "Moderation labels applied to this account.",
+          "items": {
+            "properties": {
+              "cid": {
+                "description": "CID of the labelled record version.",
+                "type": "string"
+              },
+              "cts": {
+                "description": "ISO 8601 timestamp when the label was created.",
+                "type": "string"
+              },
+              "src": {
+                "description": "DID of the labeler that issued this label.",
+                "type": "string"
+              },
+              "uri": {
+                "description": "AT-URI of the subject that was labelled.",
+                "type": "string"
+              },
+              "val": {
+                "description": "Label value string (e.g. \"spam\", \"nudity\").",
+                "type": "string"
+              }
+            },
+            "required": [
+              "src",
+              "uri",
+              "cid",
+              "val",
+              "cts"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        "postsCount": {
+          "description": "Total number of posts authored by this user.",
+          "type": "number"
+        },
+        "viewer": {
+          "description": "Viewer-specific relationship data; only populated when authenticated.",
+          "properties": {
+            "blockedBy": {
+              "description": "Whether this account has blocked the authenticated user.",
+              "type": "boolean"
+            },
+            "blocking": {
+              "description": "AT-URI of the block record if the authenticated user is blocking this account.",
+              "type": "string"
+            },
+            "followedBy": {
+              "description": "AT-URI of the follow record if this account follows the authenticated user.",
+              "type": "string"
+            },
+            "following": {
+              "description": "AT-URI of the follow record if the authenticated user follows this account.",
+              "type": "string"
+            },
+            "muted": {
+              "description": "Whether the authenticated user has muted this account.",
+              "type": "boolean"
+            }
+          },
+          "type": "object"
+        }
+      },
+      "required": [
+        "did",
+        "handle"
+      ],
+      "type": "object"
+    },
+    "success": {
+      "description": "Whether the profile was retrieved successfully.",
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "success",
+    "profile"
+  ],
+  "type": "object"
+}

Changed1 schema field changedv0.3.0Jun 9, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
First observedv0.2.1Jun 2, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already declare readOnlyHint and openWorldHint. Description adds behavioral details beyond annotations: lists exact fields returned, explains that authenticated calls include viewer-specific fields (following, followedBy, muted, blocking, blockedBy), and mentions rate limiting. No contradiction; adds value.

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 sentences, each earning its place: first sentence states core function and output, second adds authentication nuance, third provides alternatives and rate limit info. Front-loaded with essential info, no redundancy.

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

Completeness5/5

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

For a simple read tool with one required param and an output schema, the description covers all key aspects: purpose, return fields, auth behavior, alternatives, and rate limiting. No gaps. Sibling tools are numerous but differentiated well.

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 coverage is 100% with a clear description of the 'actor' parameter (handle or DID). Description does not add additional semantic meaning beyond what the schema already provides. Baseline 3 is appropriate since the schema does the heavy lifting.

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?

Description clearly states the tool retrieves a user profile from AT Protocol and lists key fields (handle, display name, bio, etc.). It distinguishes itself from siblings by noting auth-dependent richness and explicitly names alternatives (get_user_summary, get_user_connections). The verb 'retrieve' plus resource 'user profile' is specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit guidance: works without auth but is richer with auth; recommends get_user_summary for condensed overview and get_user_connections for follower/following lists. Also mentions rate limiting. Tells when and when not to use this tool effectively.

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