Skip to main content
Glama

update_configuration

Update Signal messaging settings for read receipts, typing indicators, link previews, and sealed sender indicators. Changes apply instantly and persist across sessions.

Instructions

Update Signal account-wide messaging settings. Only works when signal-mcp is the account's primary device — fails with 'This command doesn't work on linked devices' if signal-mcp was set up via signal-cli link. read_receipts controls whether Signal tells senders when you have read their messages. typing_indicators controls whether contacts see the '...' indicator when you are composing. link_previews controls whether URLs in outgoing messages generate inline previews. unidentified_delivery_indicators controls whether sealed-sender delivery icons are shown. All parameters are optional — omit any setting you do not want to change. Changes take effect immediately and persist across sessions. signal-cli has no way to read back current values — track what you've set yourself if needed. Use update_account for account-level privacy settings (discoverability, username). Do NOT use to change your profile name or photo — use update_profile for that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
link_previewsNoEnable/disable link previews in messages
read_receiptsNoEnable/disable sending read receipts
typing_indicatorsNoEnable/disable sending typing indicators
unidentified_delivery_indicatorsNoShow/hide sealed sender indicators
Install Server

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It discloses the linked-device limitation, immediate and persistent effects, and the lack of read-back. Minor omission: doesn't mention potential permission requirements, but overall transparent for a write operation.

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 thorough yet efficient. Each sentence adds distinct information—purpose, constraints, parameter meanings, alternatives. Front-loaded with the primary purpose, and 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?

Given no output schema and no annotations, the description covers all needed context: what the tool does, when to use it, limitations, parameter semantics, and differentiation from siblings. An agent can call it correctly without ambiguity.

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%, so baseline is 3. The description adds plain-language explanations of each parameter's effect (e.g., 'read_receipts controls whether Signal tells senders...') beyond the schema's brief descriptions, providing genuine added value.

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 verb+resource: 'Update Signal account-wide messaging settings.' It names specific sibling tools (update_account, update_profile) to differentiate scope, making it unambiguous.

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 tells when to use (account-wide messaging settings) and when not (profile name/photo, account-level privacy), naming the alternative tools. Also notes the primary-device requirement and failure mode.

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

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