Skip to main content
Glama
Sign In
1msg MCP

1msg MCP

Official
by 1msg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

create_settings

Update channel settings such as webhook URLs, acknowledgements, and link tracking. Send only the fields you want to change; an empty or repeated URL list clears webhooks.

Instructions

Update channel settings. Only send fields you want to change.

webhookUrl replaces the stored list (one URL string, or up to 5 URLs as an array). Passing an empty value clears webhooks. Repeating the same URL(s) also clears a sticky auto-disable. With several URLs, send the complete array to re-enable one of them — omitting a URL removes it from the channel.

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_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawHooksNo
webhookUrlNo
guaranteedHooksNo
ackNotificationsOnNo
template_analytics_enabledNo
cta_url_link_tracking_opted_outNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.10

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does substantial work: it discloses that webhookUrl replaces rather than appends, that empty values clear webhooks, the 5-URL cap, that repeats clear a sticky auto-disable, and that omission removes a URL. It stops short of stating overall mutation impact or required auth for the other settings.

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?

The intent line is front-loaded and the remaining text is dense with actionable detail rather than filler. Slightly verbose line-broken formatting around the webhookUrl rules, but every sentence earns its place.

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

Completeness2/5

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

This is a 6-parameter mutation tool with no annotations and no output schema, so the description must cover behavior fully. It thoroughly documents one parameter and omits the other five and any return/error behavior, which is not enough for an agent to call it confidently.

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

Parameters2/5

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

Schema description coverage is 0% for 6 parameters, so the description must compensate. It explains webhookUrl in useful depth (string vs array, empty-clears, replacement semantics) but says nothing about rawHooks, guaranteedHooks, ackNotificationsOn, template_analytics_enabled, or cta_url_link_tracking_opted_out, leaving five parameters undocumented anywhere.

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?

"Update channel settings" gives a clear verb and resource, and the following sentences constrain scope to partial updates. It does not, however, distinguish this from siblings like set_webhook, get_webhook, or list_settings, nor does the name (create_settings) help since the body describes an update.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Only send fields you want to change" implies partial-update usage, and the webhookUrl notes imply when to send full arrays. There is no explicit when-to-use-this-vs-set_webhook/list_settings guidance and no statement of prerequisites or permissions.

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