Skip to main content
Glama

Groups Create

groups_create
Destructive

Create 1–100 groups from 2–100 ungrouped top-level components each on a Datastudio page, with conflict-checked, journaled writes and undo.

Instructions

Create 1–100 ordinary groups from disjoint ungrouped top-level components.

Each group needs 2–100 members. Static canvas only; no regroup/nesting. Defaults come from the native editor. Grouping changes control/filter scope. Preview IDs are provisional; saved component payloads/order stay untouched. report_refresh first, page_get fingerprint, one journaled page write and undo.

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": {
      "page_id": "<page_id>",
      "groups": "<groups>",
      "expected_fingerprint": "<expected_fingerprint>"
    },
    "name": "groups_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
groupsYes
dry_runNo
page_idYes
report_idNo
expected_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the semantic side effect (grouping changes control/filter scope), bounds the destruction (saved component payloads and order stay untouched), and describes the write model (one journaled page write, undo available). It also warns that preview IDs are provisional and that defaults come from the native editor, which prevents false assumptions about generated IDs.

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?

Purpose and hard limits are front-loaded and almost every clause carries information. The final sentence is telegraphic to the point of ambiguity ("report_refresh first, page_get fingerprint, one journaled page write and undo"), forcing the reader to reconstruct the workflow.

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 destructive, batch-mutating tool with an output schema, it covers scope, side effects, atomicity, and undo, so an agent knows what changes and how to recover. Remaining gaps — permission requirements and any pagination/failure behavior under batch limits — are modest given the annotations and output 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 0%, so the description carries the burden, and it only hints indirectly: "page_get fingerprint" implies expected_fingerprint's source, "report_refresh first" implies report_id, and "preview IDs are provisional" implies dry_run behavior. page_id and the groups structure are never explained in the description, and the cardinality notes merely restate schema minItems/maxItems.

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 ... ordinary groups") plus scope constraints: 1-100 groups, 2-100 members each, drawn from disjoint ungrouped top-level components, static canvas only, no regroup/nesting. The "ordinary" and "no nesting" qualifiers implicitly separate it from groups_move, groups_ungroup, and groups_filters work.

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?

Gives a clear operating context (static canvas only, ungrouped top-level components, no nesting) and a prerequisite sequence: report_refresh first, then page_get for the fingerprint, then one journaled write. It stops short of naming sibling alternatives explicitly (e.g., groups_ungroup to reverse) or stating when-not to use it.

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