Skip to main content
Glama
cameronrye

AT Protocol MCP Server

by cameronrye
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

update_profile

DestructiveIdempotent

Update your AT Protocol profile by changing display name, bio, avatar, or banner image. Preserves existing fields not specified; requires prior blob upload for images.

Instructions

Update user profile on AT Protocol. Modifies the display name, description, avatar, and/or banner of the authenticated account; unspecified fields are preserved from the existing profile. Use upload_image to prepare blob values for avatar or banner before calling this tool. Requires authentication (app password). Subject to per-tool rate limiting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
displayNameNoNew display name for the profile (max 64 graphemes; emoji count as one). Omit to leave unchanged.
descriptionNoNew bio/description for the profile (max 256 graphemes; emoji count as one). Omit to leave unchanged.
avatarNoNew avatar image as a pre-uploaded blob descriptor: pass the `image.blob` object returned by upload_image verbatim. Omit to keep the existing avatar.
bannerNoNew banner/header image as a pre-uploaded blob descriptor: pass the `image.blob` object returned by upload_image verbatim. Omit to keep the existing banner.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successYesWhether the profile was successfully updated.
messageYesHuman-readable result message.
updatedFieldsYesNames of the profile fields that were actually changed (e.g. ["displayName", "description"]).
profileYesThe new values of the updated profile fields.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.6.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / avatar / additionalProperties
      Removed value: -false
    • changedInput schema / properties / avatar / properties / ref / anyOf
      Previous value: -[
-  {
-    "description": "CID of the uploaded blob as a flat string (e.g. \"bafkrei…\").",
-    "minLength": 1,
-    "type": "string"
-  },
-  {
-    "additionalProperties": false,
-    "description": "Lexicon blob-ref object wrapping the CID as { \"$link\": \"<cid>\" }.",
-    "properties": {
-      "$link": {
-        "description": "CID of the uploaded blob (e.g. \"bafkrei…\").",
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "$link"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "description": "CID of the uploaded blob as a flat string (e.g. \"bafkrei…\").",
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "description": "Lexicon blob-ref object wrapping the CID as { \"$link\": \"<cid>\" }.",
+    "properties": {
+      "$link": {
+        "description": "CID of the uploaded blob (e.g. \"bafkrei…\").",
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "$link"
+    ],
+    "type": "object"
+  }
+]
    • addedInput schema / properties / avatar / properties / size / maximum
      Added value: +9007199254740991
    • removedInput schema / properties / banner / additionalProperties
      Removed value: -false
    • changedInput schema / properties / banner / properties / ref / anyOf
      Previous value: -[
-  {
-    "description": "CID of the uploaded blob as a flat string (e.g. \"bafkrei…\").",
-    "minLength": 1,
-    "type": "string"
-  },
-  {
-    "additionalProperties": false,
-    "description": "Lexicon blob-ref object wrapping the CID as { \"$link\": \"<cid>\" }.",
-    "properties": {
-      "$link": {
-        "description": "CID of the uploaded blob (e.g. \"bafkrei…\").",
-        "minLength": 1,
-        "type": "string"
-      }
-    },
-    "required": [
-      "$link"
-    ],
-    "type": "object"
-  }
-]New value: +[
+  {
+    "description": "CID of the uploaded blob as a flat string (e.g. \"bafkrei…\").",
+    "minLength": 1,
+    "type": "string"
+  },
+  {
+    "description": "Lexicon blob-ref object wrapping the CID as { \"$link\": \"<cid>\" }.",
+    "properties": {
+      "$link": {
+        "description": "CID of the uploaded blob (e.g. \"bafkrei…\").",
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "$link"
+    ],
+    "type": "object"
+  }
+]
    • addedInput schema / properties / banner / properties / size / maximum
      Added value: +9007199254740991
  2. Changed15 schema fields changedv0.6.0
    • addedInput schema / properties / avatar / additionalProperties
      Added value: +false
    • addedInput schema / properties / avatar / description
      Added value: +"New avatar image as a pre-uploaded blob descriptor: pass the `image.blob` object returned by upload_image verbatim. Omit to keep the existing avatar."
    • addedInput schema / properties / avatar / properties
      Added value: +{
+  "mimeType": {
+    "description": "MIME type of the uploaded blob (e.g. \"image/jpeg\").",
+    "minLength": 1,
+    "type": "string"
+  },
+  "ref": {
+    "anyOf": [
+      {
+        "description": "CID of the uploaded blob as a flat string (e.g. \"bafkrei…\").",
+        "minLength": 1,
+        "type": "string"
+      },
+      {
+        "additionalProperties": false,
+        "description": "Lexicon blob-ref object wrapping the CID as { \"$link\": \"<cid>\" }.",
+        "properties": {
+          "$link": {
+            "description": "CID of the uploaded blob (e.g. \"bafkrei…\").",
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "$link"
+        ],
+        "type": "object"
+      }
+    ],
+    "description": "CID reference of the uploaded blob: either the flat string returned by upload_image, or the lexicon { \"$link\": \"<cid>\" } object form."
+  },
+  "size": {
+    "description": "Size of the uploaded blob in bytes.",
+    "exclusiveMinimum": 0,
+    "type": "integer"
+  },
+  "type": {
+    "const": "blob",
+    "description": "Discriminator emitted by upload_image; always \"blob\" when present. May be omitted.",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / avatar / required
      Added value: +[
+  "ref",
+  "mimeType",
+  "size"
+]
    • addedInput schema / properties / avatar / type
      Added value: +"object"
    • addedInput schema / properties / banner / additionalProperties
      Added value: +false
    • addedInput schema / properties / banner / description
      Added value: +"New banner/header image as a pre-uploaded blob descriptor: pass the `image.blob` object returned by upload_image verbatim. Omit to keep the existing banner."
    • addedInput schema / properties / banner / properties
      Added value: +{
+  "mimeType": {
+    "description": "MIME type of the uploaded blob (e.g. \"image/jpeg\").",
+    "minLength": 1,
+    "type": "string"
+  },
+  "ref": {
+    "anyOf": [
+      {
+        "description": "CID of the uploaded blob as a flat string (e.g. \"bafkrei…\").",
+        "minLength": 1,
+        "type": "string"
+      },
+      {
+        "additionalProperties": false,
+        "description": "Lexicon blob-ref object wrapping the CID as { \"$link\": \"<cid>\" }.",
+        "properties": {
+          "$link": {
+            "description": "CID of the uploaded blob (e.g. \"bafkrei…\").",
+            "minLength": 1,
+            "type": "string"
+          }
+        },
+        "required": [
+          "$link"
+        ],
+        "type": "object"
+      }
+    ],
+    "description": "CID reference of the uploaded blob: either the flat string returned by upload_image, or the lexicon { \"$link\": \"<cid>\" } object form."
+  },
+  "size": {
+    "description": "Size of the uploaded blob in bytes.",
+    "exclusiveMinimum": 0,
+    "type": "integer"
+  },
+  "type": {
+    "const": "blob",
+    "description": "Discriminator emitted by upload_image; always \"blob\" when present. May be omitted.",
+    "type": "string"
+  }
+}
    • addedInput schema / properties / banner / required
      Added value: +[
+  "ref",
+  "mimeType",
+  "size"
+]
    • addedInput schema / properties / banner / type
      Added value: +"object"
    • addedInput schema / properties / description / description
      Added value: +"New bio/description for the profile (max 256 graphemes; emoji count as one). Omit to leave unchanged."
    • removedInput schema / properties / description / maxLength
      Removed value: -256
    • addedInput schema / properties / displayName / description
      Added value: +"New display name for the profile (max 64 graphemes; emoji count as one). Omit to leave unchanged."
    • removedInput schema / properties / displayName / maxLength
      Removed value: -64
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "message": {
+      "description": "Human-readable result message.",
+      "type": "string"
+    },
+    "profile": {
+      "description": "The new values of the updated profile fields.",
+      "properties": {
+        "avatar": {
+          "description": "Set to \"updated\" when a new avatar blob was set.",
+          "type": "string"
+        },
+        "banner": {
+          "description": "Set to \"updated\" when a new banner blob was set.",
+          "type": "string"
+        },
+        "description": {
+          "description": "Updated bio/description, if it was changed.",
+          "type": "string"
+        },
+        "displayName": {
+          "description": "Updated display name, if it was changed.",
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "success": {
+      "description": "Whether the profile was successfully updated.",
+      "type": "boolean"
+    },
+    "updatedFields": {
+      "description": "Names of the profile fields that were actually changed (e.g. [\"displayName\", \"description\"]).",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "success",
+    "message",
+    "updatedFields",
+    "profile"
+  ],
+  "type": "object"
+}
  3. Changed1 schema field changedv0.3.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  4. First observedv0.2.1

TDQS

A4.5/5.0
Behavior4/5

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

The description adds important context beyond the annotations: 'unspecified fields are preserved from the existing profile' clarifies partial update semantics. Annotations already provide destructiveHint, idempotentHint, and openWorldHint, but the description adds the preservation behavior and authentication note.

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 concise, with four sentences that each add necessary information (purpose, behavior, prerequisite, auth/rate limits). It is front-loaded with the core update action, and every sentence earns its place.

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?

Given the presence of an output schema (not shown), the description does not need to cover return values. It comprehensively covers purpose, parameters, behavior, prerequisites, authentication, and rate limiting. The sibling tools list includes get_user_profile and upload_image, which are appropriately referenced.

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 100% description coverage with detailed parameter descriptions. The description adds value by explaining that omitting a parameter leaves it unchanged, and by stating the prerequisite of using upload_image for avatar/banner blobs. This exceeds the baseline of 3.

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 clearly states 'Update user profile on AT Protocol' and enumerates the specific fields that can be modified (display name, description, avatar, banner). This provides a specific verb and resource, and implicitly distinguishes from the sibling get_user_profile tool which is read-only.

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

Usage Guidelines4/5

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

The description gives explicit prerequisites: 'Use upload_image to prepare blob values for avatar or banner before calling this tool.' It also notes authentication requirements and rate limiting. While it does not explicitly state when not to use, the context implies it is for authenticated profile updates, and alternatives like get_user_profile exist for reading.

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