Skip to main content
Glama
AdsPower

AdsPower LocalAPI MCP Server

Official

update-group

Modify browser group settings in AdsPower by changing the group name and adding optional remarks to organize browser profiles more effectively.

Instructions

Update the browser group

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
groupIdYesThe id of the group to update, must be a numeric string (e.g., "123"). You can use the get-group-list tool to get the group list
groupNameYesThe new name of the group
remarkNoThe new remark of the group

Implementation Reference

  • The main handler function for the 'update-group' tool. It constructs a request body with groupId, groupName, and optional remark, sends a POST request to the UPDATE_GROUP API endpoint, and returns a success message or throws an error.
    async updateGroup({ groupId, groupName, remark }: UpdateGroupParams) {
        const requestBody: Record<string, any> = {
            group_id: groupId,
            group_name: groupName
        };
        
        if (remark !== undefined) {
            requestBody.remark = remark;
        }
    
        const response = await axios.post(`${LOCAL_API_BASE}${API_ENDPOINTS.UPDATE_GROUP}`, requestBody);
        
        if (response.data.code === 0) {
            return `Group updated successfully with id: ${groupId}, name: ${groupName}${remark !== undefined ? `, remark: ${remark === null ? '(cleared)' : remark}` : ''}`;
        }
        throw new Error(`Failed to update group: ${response.data.msg}`);
    },
  • Zod schema defining the input parameters for the 'update-group' tool: groupId (required numeric string), groupName (required string), remark (optional nullable string).
    updateGroupSchema: z.object({
        groupId: z.string()
            .regex(/^\d+$/, "Group ID must be a numeric string")
            .describe('The id of the group to update, must be a numeric string (e.g., "123"). You can use the get-group-list tool to get the group list'),
        groupName: z.string().describe('The new name of the group'),
        remark: z.string().nullable().optional().describe('The new remark of the group')
    }).strict(),
  • Registers the 'update-group' tool with the MCP server, providing name, description, input schema, and wrapped handler.
    server.tool('update-group', 'Update the browser group', schemas.updateGroupSchema.shape,
        wrapHandler(groupHandlers.updateGroup));
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Update' implies mutation, but it doesn't specify what happens to existing data not mentioned (like other group properties), whether changes are reversible, permission requirements, or error conditions. This is inadequate for a mutation tool with zero annotation coverage.

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's appropriately sized and front-loaded with the core action, making it easy to parse quickly.

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?

For a mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what the tool returns, error handling, side effects, or how it interacts with other tools (like get-group-list for obtaining groupId). The 100% schema coverage helps, but doesn't compensate for missing behavioral context.

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%, so the schema already documents all three parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema, meeting the baseline of 3 when schema does the heavy lifting.

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 verb 'update' and the resource 'browser group', making the purpose understandable. It distinguishes from siblings like 'create-group' (creation) and 'get-group-list' (read), but doesn't explicitly differentiate from 'update-browser' which updates a browser rather than a group.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a group ID from get-group-list), when not to use it, or how it differs from similar tools like update-browser.

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