GoodSender

Create Group

create_group

Create a new group of recipients.

Recipient groups are used to specify multiple recipients for an email or email template in a reusable way. Group members can be added and removed after the group is created using the 'add_group_members' and 'remove_group_members' tools. After successful creation, the group can be used for enqueuing emails or creating email templates.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "GroupName": "VIP",
      "Recipients": [
        {
          "Name": "Ada Lovelace",
          "Address": "ada@example.com"
        },
        {
          "Address": "bob@example.com"
        }
      ]
    },
    "name": "create_group"
  }
}

Input Schema

Name	Required	Description	Default
`GroupName`	Yes	Name for the new group.
`Recipients`	Yes	Recipients to add to the group. May be empty. Any pre-existing recipient names are updated with the provided names.

Output Schema

Name	Required	Description	Default
`Result`	Yes	Result of the operation.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 2, 2026
- addedInput schema / properties / Recipients / items / properties / Address / description
```
Added value: +"Email address, e.g. ada@example.com."
```
- addedInput schema / properties / Recipients / items / properties / Name / description
```
Added value: +"Optional display name shown with the address, e.g. Ada Lovelace."
```
First observedNov 2, 2026

TDQS

A3.9/5.0

Behavior3/5

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

Annotations already declare this as a non-read-only, non-destructive, non-idempotent creation operation. The description adds useful lifecycle context: members can be managed afterward and the group becomes usable for enqueuing emails or creating templates. However, it does not disclose duplicate-name behavior or other operational caveats that matter for a non-idempotent create tool.

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 description is front-loaded with the core action and then provides just enough lifecycle context. It is efficient and readable, though the four sentences could be slightly tightened without losing meaning.

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

Completeness4/5

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

Because the schema is fully described and an output schema exists, the description does not need to explain parameter formats or return values. It covers the purpose, reuse model, and post-creation workflow adequately, leaving only minor gaps such as duplicate-group handling.

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%, and the schema includes clear descriptions and examples for GroupName and Recipients. The tool description itself does not add parameter meaning beyond the schema, so the baseline of 3 applies.

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 opens with a specific verb and resource: 'Create a new group of recipients.' It immediately clarifies the resource as a reusable recipient group, which distinguishes it from individual-recipient tools such as create_recipients. An agent can understand what the tool does without opening the schema.

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

Usage Guidelines4/5

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

The description explains the intended use of recipient groups for emails and templates in a reusable way, and it names add_group_members and remove_group_members for post-creation member management. It does not explicitly contrast with create_recipients or state when not to use this tool, so it stops short of full alternative-routing guidance.

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

All GoodSender tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.