Proof Holdings

create_profile

Destructive

Create a new profile with optional display name, bio, avatar, business info, email branding (theme, support email), and theme settings.

ACCESS: needs a Proof account. Authenticate this client (Claude Code: /mcp → Authenticate), then call this tool again. start_login does NOT open this tool.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_profile"
  }
}

Input Schema

Name	Required	Description
`bio`	No	Profile bio
`theme`	No	Profile theme settings
`is_public`	No	Whether the profile is publicly visible
`avatar_url`	No	Avatar as base64 data URI or URL (~75KB limit)
`is_primary`	No	Set as primary profile
`email_theme`	No	Theme of this sub-account's emails
`is_business`	No	Whether this is a business profile
`display_name`	No	Display name
`business_name`	No	Business name
`support_email`	No	Support email this sub-account's messages show

Output Schema

Name	Required	Description
`id`	Yes	MongoDB ObjectId
`bio`	No
`theme`	Yes	Profile theme customization
`username`	No	Absent until a username is claimed
`is_public`	Yes
`avatar_url`	No	A URL or a data URI; null once cleared
`created_at`	Yes
`is_primary`	Yes
`profile_id`	Yes	The public id used in profile URLs
`updated_at`	Yes
`view_count`	Yes
`email_theme`	Yes	Theme of this sub-account's emails; null when unset (read as `dark`).
`is_business`	Yes
`proof_order`	Yes	Who decided the order of a profile's proofs. `default`: domain, social account, Telegram bot, email, phone, wallet, then each proof's `display_order`. `owner`: the owner's `display_order` alone — send it when the owner reorders. The first shown proof that is not hidden leads the profile's preview card, share tags and badge. Omitted on an update, the profile keeps its current setting.
`custom_links`	Yes
`display_name`	No
`business_name`	No
`public_proofs`	Yes	The shown proofs, in the order the public profile shows them
`support_email`	Yes	Support address shown in this sub-account's messages; null when unset.
`show_delegations`	Yes
`verification_level`	Yes	Always 'basic'; no levels are computed; removed in the next major.
`show_proof_channels`	Yes
`show_verification_dates`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 2, 2026

changedInput schema / properties / email_theme / description

Previous value: -"Theme of this project's emails"New value: +"Theme of this sub-account's emails"

changedInput schema / properties / support_email / description

Previous value: -"Support email this project's messages show"New value: +"Support email this sub-account's messages show"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "description": "A sub-account as its owner sees it",
+  "properties": {
+    "avatar_url": {
+      "description": "A URL or a data URI; null once cleared",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "bio": {
+      "type": "string"
+    },
+    "business_name": {
+      "type": "string"
+    },
+    "created_at": {
+      "type": "string"
+    },
+    "custom_links": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "_id": {
+            "type": "string"
+          },
+          "display_order": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "icon": {
+            "type": "string"
+          },
+          "is_visible": {
+            "type": "boolean"
+          },
+          "title": {
+            "type": "string"
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "_id",
+          "title",
+          "url",
+          "is_visible",
+          "display_order"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "display_name": {
+      "type": "string"
+    },
+    "email_theme": {
+      "description": "Theme of this sub-account's emails; null when unset (read as `dark`).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "id": {
+      "description": "MongoDB ObjectId",
+      "type": "string"
+    },
+    "is_business": {
+      "type": "boolean"
+    },
+    "is_primary": {
+      "type": "boolean"
+    },
+    "is_public": {
+      "type": "boolean"
+    },
+    "profile_id": {
+      "description": "The public id used in profile URLs",
+      "type": "string"
+    },
+    "proof_order": {
+      "description": "Who decided the order of a profile's proofs. `default`: domain, social account, Telegram bot, email, phone, wallet, then each proof's `display_order`. `owner`: the owner's `display_order` alone — send it when the owner reorders. The first shown proof that is not hidden leads the profile's preview card, share tags and badge. Omitted on an update, the profile keeps its current setting.",
+      "type": "string"
+    },
+    "public_proofs": {
+      "description": "The shown proofs, in the order the public profile shows them",
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "asset_id": {
+            "type": "string"
+          },
+          "channel": {
+            "type": "string"
+          },
+          "delegate_type": {
+            "type": "string"
+          },
+          "delegation_id": {
+            "type": "string"
+          },
+          "display_order": {
+            "maximum": 9007199254740991,
+            "minimum": -9007199254740991,
+            "type": "integer"
+          },
+          "display_value": {
+            "type": "string"
+          },
+          "is_revoked": {
+            "type": "boolean"
+          },
+          "is_visible": {
+            "type": "boolean"
+          },
+          "label": {
+            "type": "string"
+          },
+          "mask_level": {
+            "type": "string"
+          },
+          "type": {
+            "type": "string"
+          },
+          "verified_at": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "asset_id",
+          "type",
+          "display_value",
+          "verified_at",
+          "is_visible",
+          "display_order",
+          "mask_level"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "show_delegations": {
+      "type": "boolean"
+    },
+    "show_proof_channels": {
+      "type": "boolean"
+    },
+    "show_verification_dates": {
+      "type": "boolean"
+    },
+    "support_email": {
+      "description": "Support address shown in this sub-account's messages; null when unset.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "theme": {
+      "additionalProperties": {},
+      "description": "Profile theme customization",
+      "properties": {
+        "background_color": {
+          "type": "string"
+        },
+        "background_type": {
+          "type": "string"
+        },
+        "font_style": {
+          "type": "string"
+        },
+        "gradient_end": {
+          "type": "string"
+        },
+        "gradient_start": {
+          "type": "string"
+        },
+        "primary_color": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "updated_at": {
+      "type": "string"
+    },
+    "username": {
+      "description": "Absent until a username is claimed",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "verification_level": {
+      "description": "Always 'basic'; no levels are computed; removed in the next major.",
+      "type": "string"
+    },
+    "view_count": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    }
+  },
+  "required": [
+    "id",
+    "profile_id",
+    "is_primary",
+    "verification_level",
+    "is_business",
+    "public_proofs",
+    "proof_order",
+    "custom_links",
+    "theme",
+    "is_public",
+    "show_verification_dates",
+    "show_proof_channels",
+    "show_delegations",
+    "support_email",
+    "email_theme",
+    "view_count",
+    "created_at",
+    "updated_at"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedOct 26, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- addedInput schema / properties / support_email / pattern
```
Added value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
```
- removedInput schema / properties / theme / additionalProperties
```
Removed value: -false
```

Changed2 schema fields changedOct 16, 2026

addedInput schema / properties / email_theme

Added value: +{
+  "description": "Theme of this project's emails",
+  "enum": [
+    "dark",
+    "light"
+  ],
+  "type": "string"
+}

addedInput schema / properties / support_email

Added value: +{
+  "description": "Support email this project's messages show",
+  "format": "email",
+  "maxLength": 254,
+  "type": "string"
+}

First observedSep 19, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, and the description adds the auth requirement, which is genuinely useful. It does not disclose what happens if a profile already exists, whether setting is_primary demotes the current primary profile, or any limits on profile count.

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?

Two short blocks: purpose first, then the access prerequisite. No filler, and the blocking auth condition is stated before the agent wastes a call.

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

Completeness4/5

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

For a 10-parameter, zero-required creation tool with full schema coverage, an output schema, and annotations, the definition covers purpose and the auth gate well. Missing only secondary semantics such as defaults for optional booleans and conflict behavior.

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 every parameter including the nested theme object is already documented. The description only restates the field list without adding defaults (e.g. is_public, is_primary behavior) beyond the schema. Baseline 3 applies.

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?

Clear verb+resource ("Create a new profile") with an enumeration of optional fields matching the schema. It distinguishes itself from update_profile/delete_profile by the verb, but never names those siblings explicitly.

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?

Gives a concrete prerequisite: a Proof account is needed, and the agent must authenticate and retry rather than calling start_login. That is real when/how-to guidance. It lacks guidance on when to create vs. update an existing profile or how this relates to create_account.

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

All Proof Holdings tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.