Group same-parent SVG elements or ungroup one non-layer group while preserving child order and rejecting broken href references.
Groups same-parent SVG elements or ungroups one non-layer group while preserving child order and rejecting broken href references.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| ids | Yes | ||
| action | Yes | ||
| revision | Yes | ||
| backupCreated | Yes |
Changes observed during successful MCP inspections.
v0.1.0Input schema / oneOfPrevious value: -[
- {
- "properties": {
- "action": {
- "const": "group",
- "type": "string"
- },
- "expectedRevision": {
- "pattern": "^[a-f0-9]{64}$",
- "type": "string"
- },
- "groupId": {
- "pattern": "^[A-Za-z_][A-Za-z0-9_.-]{0,127}$",
- "type": "string"
- },
- "ids": {
- "items": {
- "pattern": "^[A-Za-z_][A-Za-z0-9_.-]{0,127}$",
- "type": "string"
- },
- "maxItems": 100,
- "minItems": 1,
- "type": "array"
- },
- "path": {
- "maxLength": 1024,
- "minLength": 1,
- "type": "string"
- },
- "workspaceId": {
- "pattern": "^ws_[a-f0-9]{16}$",
- "type": "string"
- }
- },
- "required": [
- "action",
- "expectedRevision",
- "groupId",
- "ids",
- "path",
- "workspaceId"
- ],
- "type": "object"
- },
- {
- "properties": {
- "action": {
- "const": "ungroup",
- "type": "string"
- },
- "expectedRevision": {
- "pattern": "^[a-f0-9]{64}$",
- "type": "string"
- },
- "groupId": {
- "pattern": "^[A-Za-z_][A-Za-z0-9_.-]{0,127}$",
- "type": "string"
- },
- "path": {
- "maxLength": 1024,
- "minLength": 1,
- "type": "string"
- },
- "workspaceId": {
- "pattern": "^ws_[a-f0-9]{16}$",
- "type": "string"
- }
- },
- "required": [
- "action",
- "expectedRevision",
- "groupId",
- "path",
- "workspaceId"
- ],
- "type": "object"
- }
-]New value: +[
+ {
+ "additionalProperties": false,
+ "properties": {
+ "action": {
+ "const": "group",
+ "type": "string"
+ },
+ "expectedRevision": {
+ "pattern": "^[a-f0-9]{64}$",
+ "type": "string"
+ },
+ "groupId": {
+ "pattern": "^[A-Za-z_][A-Za-z0-9_.-]{0,127}$",
+ "type": "string"
+ },
+ "ids": {
+ "items": {
+ "pattern": "^[A-Za-z_][A-Za-z0-9_.-]{0,127}$",
+ "type": "string"
+ },
+ "maxItems": 100,
+ "minItems": 1,
+ "type": "array"
+ },
+ "path": {
+ "maxLength": 1024,
+ "minLength": 1,
+ "type": "string"
+ },
+ "workspaceId": {
+ "pattern": "^ws_[a-f0-9]{16}$",
+ "type": "string"
+ }
+ },
+ "required": [
+ "action",
+ "expectedRevision",
+ "groupId",
+ "ids",
+ "path",
+ "workspaceId"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "action": {
+ "const": "ungroup",
+ "type": "string"
+ },
+ "expectedRevision": {
+ "pattern": "^[a-f0-9]{64}$",
+ "type": "string"
+ },
+ "groupId": {
+ "pattern": "^[A-Za-z_][A-Za-z0-9_.-]{0,127}$",
+ "type": "string"
+ },
+ "path": {
+ "maxLength": 1024,
+ "minLength": 1,
+ "type": "string"
+ },
+ "workspaceId": {
+ "pattern": "^ws_[a-f0-9]{16}$",
+ "type": "string"
+ }
+ },
+ "required": [
+ "action",
+ "expectedRevision",
+ "groupId",
+ "path",
+ "workspaceId"
+ ],
+ "type": "object"
+ }
+]v0.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only declare destructiveHint=true; the description adds genuinely useful behavior beyond that: child order is preserved, broken href references are rejected, and ungrouping is limited to a single non-layer group. It does not discuss atomicity or expectedRevision conflict behavior, keeping it out of 5 territory.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single dense sentence that front-loads the action and follows with the governing constraints. Every clause carries information, though the run-on construction packs three constraints together and slightly taxes readability.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With annotations (destructiveHint) and an output schema present, the description need not explain return values, and it covers the mutation's constraints and failure mode (broken hrefs). It omits anything about revision/optimistic-concurrency failure, which the expectedRevision parameter implies but does not explain.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the baseline is 3, but the description contributes real constraints the schema cannot express: the grouped elements must share a parent, and ungroup operates on exactly one non-layer group. These operational rules materially guide correct invocation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ('Groups ... SVG elements') and covers the inverse operation ('or ungroups'), so the dual group/ungroup nature mapped to the `action` enum is clear. It does not explicitly name a sibling it must be distinguished from (e.g. elements_reparent), so it falls short of a 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied through the two actions: grouping applies to 'same-parent' elements, ungrouping to 'one non-layer group'. There is no explicit statement of when to prefer this tool over siblings like elements_reparent, elements_arrange or elements_duplicate, nor any stated prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.