Skip to main content
Glama

Create an account group

create_group

Create a group inside one workspace: a named set of its channels, so a post can target all of them at once. channel_ids must belong to this workspace. A group can have a market (audience_countries, audience_world, audience_timezone): its accounts without their own market are timed for it by get_best_times.

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": {
      "workspace_id": "<workspace_id>",
      "name": "<name>"
    },
    "name": "create_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
channel_idsNo
workspace_idYesWorkspace id from list_workspaces
audience_worldNotrue: the group speaks to the whole world (overrides audience_countries)
idempotency_keyNoAny unique string you choose (REST: the Idempotency-Key header works too). Retrying with the same key and body returns the first result instead of creating a second one. Kept 24 hours.
audience_timezoneNoIANA zone of the audience, when one zone fits it
audience_countriesNoTwo-letter countries this group's accounts speak to, e.g. ["US","GB"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / audience_countries
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "pattern": "^[A-Za-z]{2}$",
      +        "type": "string"
      +      },
      +      "maxItems": 50,
      +      "type": "array"
      +    },
      +    {
      +      "pattern": "^[A-Za-z]{2}(\\s*,\\s*[A-Za-z]{2})*$",
      +      "type": "string"
      +    }
      +  ],
      +  "description": "Two-letter countries this group's accounts speak to, e.g. [\"US\",\"GB\"]"
      +}
    • addedInput schema / properties / audience_timezone
      Added value: +{
      +  "description": "IANA zone of the audience, when one zone fits it",
      +  "maxLength": 64,
      +  "type": "string"
      +}
    • addedInput schema / properties / audience_world
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "boolean"
      +    },
      +    {
      +      "enum": [
      +        "true",
      +        "false"
      +      ],
      +      "type": "string"
      +    }
      +  ],
      +  "description": "true: the group speaks to the whole world (overrides audience_countries)"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations declare a non-destructive, non-open-world write, and the description adds context beyond them: the cross-tool consequence that a group's market drives get_best_times timing for accounts lacking their own market, plus the workspace-ownership constraint on channel_ids. It does not mention what the call returns or that group creation can be retried safely via idempotency_key.

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?

Two sentences, front-loaded with the core definition before constraints and the market behavior. Dense but every clause carries information; the parenthetical market explanation is slightly compressed rather than wasteful.

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?

For a 7-parameter create tool with 71% schema coverage and annotations covering the safety profile, the description supplies purpose, scope, a hard constraint, and downstream semantics. The one gap is that with no output schema, nothing tells the agent what a successful creation returns (e.g., the new group id).

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 71%, and the description adds real meaning for the audience_* cluster by framing it as an optional "market" that affects downstream timing, a relationship the schema's field descriptions do not convey. It reinforces the workspace_id/channel_ids relationship but leaves name and idempotency_key to the schema.

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?

States a specific verb and resource ("Create a group inside one workspace") and defines what the resource is: "a named set of its channels, so a post can target all of them at once." That distinguishes it from list_groups and create_workspace without the agent opening a 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 gives the condition for creation (bundling channels so a post targets them together) and a key precondition: "channel_ids must belong to this workspace." It does not name an alternative tool or say when to avoid creating a group, so it stops short of a 5.

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