Skip to main content
Glama
googlarz

Signal MCP

by googlarz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

update_profile

Idempotent

Modify your Signal profile details like display name, bio, avatar, and MobileCoin address. Update only the fields you specify and apply changes to your Signal account.

Instructions

Change your own Signal profile, which is uploaded to Signal's servers and seen by people you share your profile with. Only the fields you pass change. name: display name (alias of given_name; given_name wins if both are set). given_name / family_name: the two parts of your profile name. about: bio text; about_emoji: emoji shown next to it. mobilecoin_address: base64-encoded MobileCoin public address. avatar_path: local image file (JPEG or PNG) inside the allowed send folders (SIGNAL_MCP_SEND_ROOTS), no hidden paths. remove_avatar (default false): clear the current photo. Returns status 'profile updated'. To label someone else locally use update_contact; to rename a linked device use update_device; for account settings use update_account.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoDisplay (given) name to set; alias of given_name
aboutNoAbout/bio text
given_nameNoProfile given name
about_emojiNoEmoji shown next to the about text
avatar_pathNoLocal JPEG/PNG path inside the allowed send folders (SIGNAL_MCP_SEND_ROOTS)
family_nameNoProfile family name
remove_avatarNoRemove current avatar
mobilecoin_addressNoMobileCoin address (base64)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.43.0
    • changedInput schema / properties / avatar_path / description
      Previous value: -"Path to avatar image file"New value: +"Local JPEG/PNG path inside the allowed send folders (SIGNAL_MCP_SEND_ROOTS)"
  2. Changed5 schema fields changedv1.40.1
    • addedInput schema / properties / about_emoji
      Added value: +{
+  "description": "Emoji shown next to the about text",
+  "type": "string"
+}
    • addedInput schema / properties / family_name
      Added value: +{
+  "description": "Profile family name",
+  "type": "string"
+}
    • addedInput schema / properties / given_name
      Added value: +{
+  "description": "Profile given name",
+  "type": "string"
+}
    • addedInput schema / properties / mobilecoin_address
      Added value: +{
+  "description": "MobileCoin address (base64)",
+  "type": "string"
+}
    • changedInput schema / properties / name / description
      Previous value: -"Display name to set"New value: +"Display (given) name to set; alias of given_name"
  3. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

With annotations already declaring readOnly=false, destructive=false, idempotent=true and openWorld=true, the description still adds material context: profile data is 'uploaded to Signal's servers and seen by people you share your profile with' (privacy exposure), 'Only the fields you pass change' (partial-update semantics), the return string, and avatar path constraints. It does not detail failure modes for invalid paths, so it stops short of 5.

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?

Purpose and sibling routing are front-loaded, and there is little waste. However, the parameter walkthrough is delivered as a single dense run-on block rather than being broken out, which slightly hurts scannability for an 8-parameter tool.

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 no-required-parameter mutation tool with no output schema, the definition covers visibility of the change, partial-update behavior, removal semantics, path restrictions, and the return value. An agent has everything needed to invoke it correctly.

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?

Schema coverage is already 100%, but the description adds real meaning beyond it: the name/given_name alias with the precedence rule ('given_name wins if both are set'), remove_avatar's default, and the allowed-roots restriction on avatar_path. That precedence rule in particular is not derivable from the schema.

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?

States a specific verb and resource ('Change your own Signal profile') and immediately scopes it to the caller's own profile versus others. It explicitly names the sibling tools it is not (update_contact, update_device, update_account), so an agent can route correctly without opening any schema.

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?

Offers explicit alternatives with the condition that selects each: 'To label someone else locally use update_contact; to rename a linked device use update_device; for account settings use update_account.' Nothing is left to inference about when to pick this tool.

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