Skip to main content
Glama
Sign In
ZennoBrowser MCP Server

ZennoBrowser MCP Server

Official
by ZennoLab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Updates the preset for multiple browser profiles.

bulk_update_profile_preset

Update the preset configuration for one or more browser profiles at once, or remove the preset by passing null.

Instructions

This method updates the preset configuration for one or more browser profiles at once.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "body": "<body>"
    },
    "name": "bulk_update_profile_preset"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyYesArray of profile IDs to update.
presetIdNoThe preset identifier to assign. Pass null to remove the preset.
workspaceIdNoWorkspace identifier. -1 means the default workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, openWorld=false, so the safety profile is covered. The description adds nothing beyond that: no batch atomicity semantics (all-or-nothing vs. partial failure), no note that assigning a preset overwrites existing preset assignments, and no permission/auth context.

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

Conciseness4/5

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

A single front-loaded sentence with no filler or redundancy. It is efficient, though it is essentially a restatement of the title rather than a substantive expansion.

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 bulk mutation tool with no output schema and no annotations covering batch behavior, the description should address partial-failure handling, batch size limits, or what 'update the preset' actually changes on each profile. None of this is present, leaving the agent under-informed about the operation's consequences.

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 all three parameters (body, presetId, workspaceId, including the null-removes-preset semantics) are documented in the schema itself. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb (updates), resource (preset configuration for browser profiles), and bulk scope (one or more profiles at once), which distinguishes it from single-profile and non-preset siblings. It does not explicitly name its closest siblings (bulk_update_profile_proxy, bulk_update_profile_tags), but the resource is unambiguous.

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 when-to-use or when-not-to-use guidance. With three near-identical bulk_update_profile_* siblings, an agent gets no help choosing between preset, proxy, and tags variants, nor any prerequisites (e.g., preset must exist, profiles must be accessible).

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

Deploy Server

Other Tools