Move selected browser profiles to a different group by providing the profile IDs and the target group ID, helping you reorganize and manage profile organization.
Move profiles to a different group.
| Name | Required | Description | Default |
|---|---|---|---|
| group_id | Yes | Target group ID ("0" for ungrouped) | |
| profile_id | Yes | Array of profile IDs to move |
Changes observed during successful MCP inspections.
v0.1.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Move' implies mutation and reassignment, but the description does not state whether profiles are removed from their current group, whether the operation is reversible or idempotent, or what happens if a profile is already in the target group. These are meaningful behavioral gaps.
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?
The description is a single front-loaded sentence with no filler words. Every word earns its place, and the core action is immediately visible.
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?
For a simple two-parameter tool, the description plus fully documented schema is nearly sufficient, but the absence of annotations and behavioral side-effect disclosure makes it only minimally complete. An agent can invoke it correctly, but may not fully understand the consequences of moving profiles.
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 description coverage is 100%, with both profile_id and group_id clearly described in the input schema. The description itself adds no parameter-level meaning beyond the schema, so the baseline of 3 is appropriate.
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?
The description uses a specific verb and resource: 'Move profiles to a different group.' It clearly states the tool's core action. However, it does not explicitly differentiate itself from sibling tools like profile_update or group_update, so it falls short of full sibling distinction.
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?
The description implies the tool is used when profiles need to be reassigned to another group, but it gives no explicit when-to-use, when-not-to-use, or alternative-tool guidance. There is no mention of prerequisites such as the target group needing to exist or whether this is preferred over profile_update for group changes.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.