Skip to main content
Glama
AdsPower

AdsPower LocalAPI MCP Server

Official

move-browser

Move browser profiles to different organizational groups within AdsPower to manage and categorize them effectively.

Instructions

Move browsers to a group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupIdYesThe target group id, must be a numeric string (e.g., "123"). You can use the get-group-list tool to get the group list
userIdsYesThe browser ids to move

Implementation Reference

  • The main handler function for the 'move-browser' tool. It sends a POST request to move browsers (by userIds) to a specified groupId and returns a success message or throws an error.
    async moveBrowser({ groupId, userIds }: MoveBrowserParams) {
        const response = await axios.post(`${LOCAL_API_BASE}${API_ENDPOINTS.MOVE_BROWSER}`, {
            group_id: groupId,
            user_ids: userIds
        });
    
        if (response.data.code === 0) {
            return `Browsers moved successfully to group ${groupId}: ${userIds.join(', ')}`;
        }
        throw new Error(`Failed to move browsers: ${response.data.msg}`);
    }
  • Zod schema defining the input parameters for the 'move-browser' tool: groupId (numeric string) and userIds (array of strings).
    moveBrowserSchema: z.object({
        groupId: z.string()
            .regex(/^\d+$/, "Group ID must be a numeric string")
            .describe('The target group id, must be a numeric string (e.g., "123"). You can use the get-group-list tool to get the group list'),
        userIds: z.array(z.string()).describe('The browser ids to move')
    }).strict(),
  • Registration of the 'move-browser' tool with MCP server, linking name, description, schema, and wrapped handler.
    server.tool('move-browser', 'Move browsers to a group', schemas.moveBrowserSchema.shape,
        wrapHandler(browserHandlers.moveBrowser));
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states a mutation action ('Move') but doesn't clarify permissions needed, whether the operation is reversible, what happens to browsers in transit (e.g., if they're active), error conditions, or side effects. This is a significant gap for a tool that modifies state without any structured safety hints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence with zero wasted words. It front-loads the core action and resource, making it immediately understandable. No extraneous details or repetition are present, which is ideal for conciseness.

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

Completeness2/5

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

Given the tool's complexity (a mutation operation with no annotations and no output schema), the description is insufficient. It lacks critical context: no information on return values, error handling, prerequisites, or behavioral traits. For a tool that moves resources between groups, this leaves the agent with significant gaps in understanding how to use it effectively.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with clear documentation for both parameters (groupId and userIds). The description adds no additional semantic context beyond what the schema provides, such as explaining what 'browser ids' represent or constraints on group selection. Baseline 3 is appropriate since the schema adequately covers parameter meanings.

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?

The description clearly states the action ('Move') and resource ('browsers to a group'), making the purpose understandable. It distinguishes from siblings like 'create-group' or 'update-group' by focusing on relocation rather than creation/modification. However, it doesn't specify what 'browsers' refer to (e.g., browser instances/sessions) or the system context, leaving some ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., browsers must exist, group must exist), exclusions (e.g., cannot move to non-existent groups), or related tools like 'get-group-list' for obtaining group IDs. The description alone offers no usage context beyond the basic action.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AdsPower/local-api-mcp-typescript'

If you have feedback or need assistance with the MCP directory API, please join our Discord server