Skip to main content
Glama

Groups Ungroup

groups_ungroup
Destructive

Ungroups ordinary containers while retaining all components and their order, removes group-local filters, and returns members to page control/filter scope; preview removed groups before applying.

Instructions

Remove ordinary group containers, retaining every component and its order.

Removes group-local filters and returns members to page control/filter scope; inspect removed_groups in preview. No nested or responsive groups. Uses report_refresh, page_get fingerprint, one journaled page write/read-back/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>",
      "group_ids": "<group_ids>",
      "expected_fingerprint": "<expected_fingerprint>"
    },
    "name": "groups_ungroup"
  }
}

Input Schema

NameRequiredDescriptionDefault
dry_runNo
page_idYes
group_idsYes
report_idNo
expected_fingerprintYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.5

TDQS

A4/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation: it discloses what survives (components and their order), what is lost (group-local filters, members returned to page scope), unsupported group types, and the transactional profile ('one journaled page write/read-back/undo', report_refresh, fingerprint check). That is exactly the context an agent needs before a destructive write.

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?

Front-loaded with the core action and outcome, then constraints, then mechanics. Dense and jargon-heavy ('report_refresh, page_get fingerprint, one journaled page write/read-back/undo') but nearly every clause carries operational information.

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 5-parameter tool this covers what is destroyed, what is preserved, unsupported cases, and the commit/undo model, and an output schema exists to explain removed_groups. Missing only permission requirements and explicit dry_run default behavior.

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?

With 0% schema description coverage, the description must compensate, and it does partially: it explains the fingerprint/refresh coupling behind expected_fingerprint and report_refresh, and the preview semantics behind dry_run and removed_groups. It never names group_ids or spells out dry_run's default, leaving some inference, but adds substantial meaning over a bare schema.

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 and resource: 'Remove ordinary group containers, retaining every component and its order.' It also bounds the operation ('No nested or responsive groups'), which helps distinguish it from group-manipulation siblings, though no sibling is named directly.

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 implied rather than stated: 'inspect removed_groups in preview' suggests a preview-then-commit workflow (consistent with dry_run defaulting to true), but the description never says when to prefer this over alternatives like groups_move or groups_filters, nor any prerequisites.

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