Skip to main content
Glama

update_group

Modify Signal group settings, membership, and permissions. Changes apply instantly; admin status required for member or link changes.

Instructions

Modify a Signal group's settings, membership, or permissions. All parameters except group_id are optional — include only what you want to change. add_members sends invitations; remove_members removes members immediately. add_admins promotes members to admin; remove_admins demotes them. expiration_seconds sets the disappearing-messages timer (0 to disable). link_mode controls the invite link: 'enabled' (anyone with link can join), 'enabled-with-approval' (admin must approve), 'disabled' (no link), or 'reset' (generate a new link and invalidate the old one). Changes are applied instantly and all members receive an update notification. You must be a group admin to change membership, admin list, or invite link. Use list_groups to get the group_id and confirm your admin status. Do NOT use to send a message — use send_group_message for that.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
group_idYesGroup ID to update
nameNoNew group name
descriptionNoNew group description
add_membersNoPhone numbers to add
remove_membersNoPhone numbers to remove
add_adminsNoPhone numbers to promote to admin
remove_adminsNoPhone numbers to demote from admin
expiration_secondsNoDisappearing message timer in seconds (0 to disable)
link_modeNoInvite link mode: 'disabled', 'enabled', 'enabled-with-approval', or 'reset' to generate a new link
Behavior5/5

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

With no annotations, the description fully carries the burden. It explains that changes are applied instantly, all members receive notification, admin is required for certain changes, and details the behavior of parameters like add_members (sends invitations) vs remove_members (removes immediately).

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 well-structured and concise, front-loaded with the main purpose, and every sentence provides essential information without 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 9 parameters, no output schema, and no annotations, the description is comprehensive: covers all parameter behaviors, side effects, prerequisites (admin), and provides cross-reference to list_groups. It fully compensates for missing annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% (baseline 3), but the description adds significant value: explains add_members sends invitations, remove_members removes immediately, add_admins promotes, remove_admins demotes, expiration_seconds sets disappearing timer (0 to disable), and link_mode options with descriptions.

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 starts with 'Modify a Signal group's settings, membership, or permissions,' which clearly states the verb (Modify) and resource (Signal group). It distinguishes from sibling tools like create_group (creates) and send_group_message (sends).

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 says 'Do NOT use to send a message — use send_group_message for that' and advises using list_groups to get the group_id and confirm admin status. Provides clear when-to and when-not-to use.

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