Skip to main content
Glama

update_account

Update your Signal account's privacy and identity settings: control discoverability, phone number sharing, set or delete a username, and manage device names.

Instructions

Update Signal account-level privacy and identity settings. All parameters are optional — only provide the settings you want to change. discoverable_by_number controls whether others can find you by phone number. number_sharing controls whether your number is shared with contacts you message. username sets a @username alias; delete_username removes it. Use get_configuration for messaging settings (read receipts, typing indicators).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
device_nameNoName for this device shown in linked devices list
discoverable_by_numberNoAllow others to find your account by phone number
number_sharingNoShare your phone number when sending messages
usernameNoSet a Signal username (without @) as an alias for your number
delete_usernameNoDelete your current Signal username
unrestricted_unidentified_senderNoAllow sealed-sender messages from anyone (not just contacts)
Behavior4/5

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

The description explains the effect of each parameter (e.g., 'discoverable_by_number controls whether others can find you', 'delete_username removes it'). No annotations provided, so description carries the burden; it covers behavior but could mention any side effects or prerequisites.

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 with a clear structure: main purpose, optional parameter reminder, parameter explanations, and alternative tool mention. No wasted words.

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?

Tool has 6 parameters, no output schema, and no annotations. Description covers all parameters sufficiently, includes usage guidance, and references an alternative tool, making it complete for agent usage.

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 100%, baseline 3. Description adds context beyond schema descriptions, e.g., clarifying that username sets a '@username alias' and delete_username removes it. Provides useful guidance.

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 Signal account-level privacy and identity settings' with a specific verb and resource. It distinguishes from sibling tool 'get_configuration' which handles messaging settings.

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?

Explicitly states all parameters are optional and advises to only provide settings to change. Includes when to use the alternative tool get_configuration for messaging settings.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/googlarz/signal-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server