Skip to main content
Glama

Groups Move

groups_move
Destructive

Translate up to 100 groups by applying equal pixel offsets to every member while preserving sizes, rotations, layer order and settings. Use it to reposition grouped report elements in one previewed, undoable page write.

Instructions

Translate 1–100 ordinary groups, preserving their members and settings.

Integer pixel offset_x/offset_y applied equally to every member. Preserves sizes, rotations, relative positions, layer order, group filters/control scope. Static canvas, direct leaf members only; nested/overlapping groups and composites rejected. A zero translation returns unchanged without writing. report_refresh first, page_get fingerprint, preview, one 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>",
      "moves": "<moves>",
      "expected_fingerprint": "<expected_fingerprint>"
    },
    "name": "groups_move"
  }
}

Input Schema

NameRequiredDescriptionDefault
movesYes
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.6/5.0
Behavior5/5

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

Annotations only say readOnly=false and destructive=true; the description adds substantial context beyond that: what is preserved (sizes, rotations, relative positions, layer order, filters/control scope), that a zero translation is a no-op with no write, that dry_run previews, and that the operation is a single page write with undo available.

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 scope, then constraints, then workflow. Dense and telegraphic in places ('report_refresh first, page_get fingerprint, preview, one page write and undo'), but nearly every clause carries operational meaning.

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

Completeness5/5

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

For a destructive 5-parameter mutation with an output schema, the description covers preconditions, rejection cases, no-op behavior, preview semantics, and undo. Return values need not be explained because an output schema exists.

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 description coverage is 0%, so the description must carry the load, and it does: offset_x/offset_y are integer pixel offsets applied equally to every member, moves targets groups, expected_fingerprint comes from page_get, and report_id ties to report_refresh. It never explicitly names dry_run's default or the fingerprint mismatch behavior, leaving a small gap.

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 ('Translate ... ordinary groups') plus scope (1–100) and what is preserved (members, settings). An agent can distinguish this from groups_create, groups_ungroup, or components_geometry without 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?

Gives explicit exclusions ('nested/overlapping groups and composites rejected', 'direct leaf members only', 'Static canvas') and a required workflow ('report_refresh first, page_get fingerprint, preview, one page write and undo'). It does not name a sibling alternative for the rejected cases, 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.

Deploy Server

Other Tools