Delete groups

Tool Name: airdroid_business_delete_groups

Risk Level: 🔴 High Risk

Execution Mode: ⚡ Synchronous

Category: Group Management

Quick Start (Copy & Use)

One-liner: Batch-delete one or more empty groups (groups with no devices).

You need: GroupIds (array of group IDs to delete), Confirm (must be true), Reason (reason for deletion)

Success criteria: StatusCode == 200 AND ErrorMessage == ""

What to do next: Confirm the groups have been deleted; no further action needed

⚠️ High-Risk Operation Warning: This operation is irreversible. Deleted groups cannot be recovered.

Minimum request example:

{
  "GroupIds": [100, 101, 102],
  "Confirm": true,
  "Reason": "Removing obsolete test groups"
}

Minimum response example:

{
  "StatusCode": 200,
  "ErrorMessage": ""
}

Recipes (Common Recipes)

Recipe 1: Delete a single empty group

Scenario: Delete a single group that is no longer in use

{
  "GroupIds": [100],
  "Confirm": true,
  "Reason": "Consolidating department groups"
}

Recipe 2: Batch-delete multiple groups

Scenario: Clean up multiple obsolete test groups

{
  "GroupIds": [100, 101, 102],
  "Confirm": true,
  "Reason": "Removing obsolete test groups after project completion"
}

Recipe 3: Move devices out first, then delete the group

Scenario: Delete a group that contains devices (must move devices out first)

Step 1: Get devices in the group

{
  "Keyword": {"group_name": "Old Group"},
  "SelectedColumns": ["device_id"]
}

Step 2: Move devices to another group

{
  "DeviceIds": [1001, 1002, 1003],
  "GroupId": 200
}

Step 3: Delete the empty group

{
  "GroupIds": [100],
  "Confirm": true,
  "Reason": "Migrated devices to new group, removing old group"
}

1. Overview

1.1 Description

Batch-delete one or more device groups in AirDroid Business. This is a high-risk operation. Only empty groups (containing no devices) can be deleted, and the deletion is irreversible.

1.2 When to Use

• Clean up obsolete groups: Remove groups that are no longer in use
• Organizational restructuring: Clean up surplus groups after merging or reorganizing the group structure
• Test cleanup: Delete temporary groups created in test environments

1.3 Execution Mode & Response

This is a synchronous operation that returns the deletion result immediately.

• Return value: StatusCode and ErrorMessage
• Typical latency: < 2 seconds

1.4 Prerequisites

1.5 Prerequisite Tools

2. Inputs

2.1 Parameter List

2.2 Parameter Details

`GroupIds`

Array of group IDs to delete.

• Type: number-array (array of integers)
• Format requirements:
  • Non-empty array
  • Each element must be a positive integer greater than 0
  • Maximum count: Up to 50 groups per request
• Source:

How to obtain:

1. Use Get a Group ID by Group Name to look up by group name
2. Use the group_id field from Get All Devices response
3. Use the id field from Get a Group response

• How to fill in a GI node:
  • Constant value: Enter an array directly, e.g. [100, 101, 102]
  • Upstream output reference: Get from Get a Group ID by Group Name output GroupIds
• Example:

[100, 101, 102]

Important: Only empty groups (device_count = 0) can be deleted.

`Confirm`

Safety confirmation parameter to prevent accidental deletion.

• Type: bool
• Format requirements: Must be explicitly set to true for deletion to proceed
• Design purpose:
  • Prevents accidental deletion from automated workflows
  • Forces the Agent to confirm user intent before calling
• How to fill in a GI node:
  • Constant value: Enter true (only after user confirmation)
• Example:

true

⚠️ Agent behavior requirements:

• Must confirm the deletion intent with the user before calling this tool
• Must set Confirm to true only after receiving explicit user consent
• Must not perform deletion without user confirmation

`Reason`

Reason for deletion, used for audit trails and compliance records.

• Type: string
• Format requirements:
  • Cannot be empty or contain only spaces
  • Should concisely explain the deletion reason
• Purpose:
  • Recorded in the system audit log
  • Facilitates post-hoc traceability
  • Satisfies compliance requirements
• How to fill in a GI node:
  • Constant value: Enter a string directly, e.g. "Consolidating regional groups"
  • Upstream output reference: Get the deletion reason from user input
• Example:

"Consolidating regional groups after org restructure"

or

"Removing obsolete test groups"

3. Outputs

3.1 Response Examples

Success response:

{
  "StatusCode": 200,
  "ErrorMessage": ""
}

Error response (not confirmed):

{
  "StatusCode": 200,
  "ErrorMessage": "Confirm must be set to true to execute deletion. This is a safety measure to prevent accidental deletion."
}

Error response (missing reason):

{
  "StatusCode": 200,
  "ErrorMessage": "Reason is required for audit trail. Provide a brief explanation for this deletion."
}

Error response (group not empty):

{
  "StatusCode": 200,
  "ErrorMessage": "Group is not empty. Move devices out first."
}

Error response (parameter error):

{
  "StatusCode": -1,
  "ErrorMessage": "GroupIds must be a non-empty array of group IDs. Obtain via 'Get a Group ID by Group Name' tool."
}

3.2 Field Descriptions

4. Examples

4.1 Basic Example: Delete a single group

Request parameters:

{
  "GroupIds": [100],
  "Confirm": true,
  "Reason": "Department no longer uses separate device group"
}

Response:

{
  "StatusCode": 200,
  "ErrorMessage": ""
}

4.2 Advanced Example: Batch-delete groups

Request parameters:

{
  "GroupIds": [100, 101, 102],
  "Confirm": true,
  "Reason": "Removing obsolete test groups after project completion"
}

Response:

{
  "StatusCode": 200,
  "ErrorMessage": ""
}

4.3 Error Example: Confirmation not set

Request parameters:

{
  "GroupIds": [100],
  "Confirm": false,
  "Reason": "Test deletion"
}

Response:

{
  "StatusCode": 200,
  "ErrorMessage": "Confirm must be set to true to execute deletion. This is a safety measure to prevent accidental deletion."
}

4.4 Error Example: Group not empty

Request parameters:

{
  "GroupIds": [100],
  "Confirm": true,
  "Reason": "Removing old group"
}

Response:

{
  "StatusCode": 200,
  "ErrorMessage": "Group is not empty. Move devices out first via 'Move Devices to a Group' tool."
}

5. Error Handling

5.1 AB Three-Layer Error Codes

Core principle: AB uses a three-layer error code strategy. The Agent should decide its handling approach based on the StatusCode.

5.2 Common Errors

5.3 Agent Self-Healing Decision Table

6. Best Practices

6.1 Performance Optimization

• Batch deletion: Delete up to 50 groups per request; leverage batch capability
• Batch processing: For more than 50 groups, split into multiple requests

6.2 Security Considerations

⚠️ High-Risk Operation Warning: This operation permanently deletes groups and cannot be undone.

Pre-execution checklist:

1. ☐ Confirm the group is empty (device_count = 0)
2. ☐ Confirm it is not the default group (is_default = "0")
3. ☐ Confirm the target is correct (verify group name and ID)
4. ☐ Obtain explicit user authorization
5. ☐ Record the deletion reason for audit

6.3 Idempotency

Idempotency of this operation: Not idempotent.

• First call: Successfully deletes the group
• Second call with same parameters: Fails because the group no longer exists
• It is recommended to use Get a Group to confirm the group exists before deleting

7. Related Tools

7.1 Prerequisite Tools

7.2 Follow-up Tools

7.3 Similar Tools Comparison

8. Tool Chains

8.1 Safe Group Deletion

Scenario: Perform safety checks before deleting a group

Tool chain:

Get a Group ID by Group Name → Get a Group → [Check] → Delete Groups

Steps:

1. Call Get a Group ID by Group Name to get the group ID
2. Call Get a Group to check group details
3. Verify device_count = 0 and is_default = "0"
4. Confirm deletion intent with the user
5. Call Delete Groups after user confirmation

8.2 Empty a Group Then Delete

Scenario: Delete a group that contains devices

Tool chain:

Get All Devices → Move Devices to a Group (batch) → Delete Groups

Steps:

1. Call Get All Devices to get all devices in the group
2. Use Move Devices to a Group to move devices to another group
3. Confirm deletion intent with the user
4. Call Delete Groups to delete the empty group

8.3 Batch Clean Up Obsolete Groups

Scenario: Clean up multiple groups that are no longer in use

Tool chain:

[Multiple] Get a Group ID by Group Name → [Collect IDs] → Delete Groups

Steps:

1. Collect all group names to delete
2. Call Get a Group ID by Group Name for each to get IDs
3. Check each group is empty
4. Confirm the deletion list with the user
5. Call Delete Groups to batch-delete (up to 50 per request)