Skip to main content
Glama

Create Group

create_group
Destructive

Create a regular or adaptive group in Mobile Text Alerts

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName of the group to create
hiddenNoWhether the group is hidden
settingsNoSettings for adaptive group with dynamic membership rules (both match and conditions required for adaptive groups)
sortOrderNoSort order for the group
descriptionNoDescription of the group
displayNameNoDisplay name of the group
isTemporaryNoWhether the group is temporary

Output Schema

NameRequiredDescriptionDefault
dataYesRaw Mobile Text Alerts API response envelope. The group payload is nested one level down, under `data.data` — e.g. `data.data.id`.
errorNo
statusYes
contextNoAdditional context about why the call was blocked
groupIdNoID of the created group
successYes
errorCodeNoMachine-readable error code. 'ONBOARDING_REQUIRED' means the account has not finished brand registration. 'NO_SENDING_NUMBER' means no number on the account can send yet; 'SENDING_NUMBER_NOT_FOUND' / 'SENDING_NUMBER_UNAVAILABLE' mean the requested `from` number is not on the account or can't send. 'AUTH_FAILED', 'RATE_LIMITED', 'UPSTREAM_ERROR' and 'UPSTREAM_UNAVAILABLE' are Mobile Text Alerts API failures.
groupNameNoName of the created group
nextStepsNoExplicit recovery guidance for the calling agent
statusTextYes
memberCountNoNumber of members in the group (0 for new groups)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations supply only destructiveHint=true and a title, so the description carries most of the burden. It usefully discloses the regular/adaptive duality, but says nothing about name uniqueness or duplicate-name behavior, permissions, or whether a failed adaptive payload is rejected — relevant for a mutation with nested rules. No contradiction with annotations, which mark the call destructive.

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?

A single short sentence with no redundant wording, and the key distinction (regular vs adaptive) is front-loaded. It is efficient but lacks any structural cue such as listing the modes or prerequisites.

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

Completeness3/5

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

An output schema exists, so return-value explanation is unnecessary, and the schema covers all 7 parameters. Still, for a mutation tool with a nested adaptive-rules object, the description should at least note that adaptive groups require the `settings` payload; without that, an agent must infer it entirely from the schema.

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

Parameters3/5

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

Schema description coverage is 100%, with nested `settings.match` and `settings.conditions` fully documented, so the schema does the heavy lifting. The description adds no additional parameter meaning and does not reinforce that both `match` and `conditions` are required for adaptive groups, leaving it at baseline.

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?

States a specific verb ('Create') and resource ('group') plus the scope 'in Mobile Text Alerts', and distinguishes the two creatable variants (regular vs adaptive). An agent immediately knows this is a creation tool for groups; only sibling-level differentiation is absent, which is a minor gap.

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?

Usage is only implied by the verb 'Create'. The mention of 'regular or adaptive' hints that two modes exist, but the definition never says how to choose between them or that the `settings` object is what makes a group adaptive. No when-not-to-use or alternative routing is given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources