Skip to main content
Glama
ZennoLab

ZennoBrowser MCP Server

Official
by ZennoLab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Creates a new browser profile in the specified workspace and folder.

create_profile

Create a new browser profile in a chosen workspace and folder, with optional settings for fingerprint, proxy, screen, language, and timezone. Returns a unique ID for updates or deletion.

Instructions

This method creates a new browser profile in the specified workspace and the folder. It is possible to customize various parameters such as screen size, hardware emulation, language, timezone, proxy, and others. All parameters are optional if another is not specified. Browser profile is a set of parameters for browser configuration that can be used to create browser instances with different fingerprints and settings. Each profile has a unique identifier that is returned upon creation and can be used for subsequent operations on the profile, such as updating or deleting.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cpuNoCPU configuration settings. Allowed values: "auto" to use value from fingerprint, "ignore" to use system value, or one of the specific core/thread strings: "2/4", "4/8", "6/12", "8/16", "10/20", "12/24", "14/28", "16/32", "32/64", "64/128". Use the exact string including the slash, e.g. "4/8" not "4".
nameNoThe profile name.
tagsNoProfile tags separated by spaces (optional).
audioNoAudio configuration settings. Allowed values: "on" to enable or "off" to disable.
fontsNoFont configuration settings. Allowed values: "on" to enable or "off" to disable.
notesNoAdditional notes for the profile.
webGlNoWebGL configuration settings. Allowed values: "auto" to use value from fingerprint, "ignore" to use system value.
canvasNoCanvas settings. The allowed values are: "Ignore" to disable this feature or "Noise" to use noising.
memoryNoMemory configuration settings. Allowed values: "auto" to use value from fingerprint, "ignore" to use system value, or one of the specific GB values as a string: "2", "4", "8", "16", "32", "64", "128".
screenNoScreen configuration settings. Allowed values: "auto" to use value from fingerprint, "ignore" to use system value, or one of the named resolution IDs: "SVGA" (800×600), "WSVGA" (1024×600), "XGA" (1024×768), "HD" (1280×720), "WXGA" (1280×768), "WXGA+" (1280×800), "SXGA" (1280×1024), "WXGA HD" (1366×768), "WSXGA" (1440×900), "HD+" (1600×900), "UXGA" (1600×1200), "WSXGA+" (1680×1050), "FHD" (1920×1080), "WUXGA" (1920×1200), "WQHD" (2560×1440), "4K UHD-1" (3840×2160), "5K" (5120×2880), "8K UHD-2" (7680×4320), and others such as "XGA+", "SXGA-", "SXGA+", "1360×768", "1536×864", "QWXGA", "QXGA", "WQXGA". Use the exact named ID string, not pixel dimensions directly.
webGpuNoWebGPU configuration settings. Allowed values: "on" to enable or "off" to disable.
webRtcNoWebRTC configuration settings. Allowed values: "Emulate" to use value from fingerprint, "Real" to use system value, or "Hide" to disable.
batteryNoBattery configuration settings. Allowed values: "on" to enable or "off" to disable.
domRectNoDOM Rectangle configuration settings. Allowed values: "Ignore" to disable or "Noise" to use dom rect noising.
pluginsNoBrowser plugins configuration. Allowed values: "on" to enable or "off" to disable.
folderIdNoFolder identifier (optional).
languageNoBrowser language settings. Allowed values: "auto" to use value from fingerprint, "ignore" to use system value, or one of the supported locale codes: "ru" (Russian), "en-US" (English US), "de" (German), "fr" (French), "es" (Spanish), "en-GB" (English UK).
presetIdNoOptional preset identifier used to initialize the profile configuration.
timeZoneNoTime zone settings. Allowed values: "auto" to use value from fingerprint, "system" to use system value, or custom timezone value (e.g., Europe/Moscow).
osVersionNoOS version for fingerprint selection. Allowed values: "win10" or "win11". If empty, the server auto-detects the host OS.
geoLocationNoGeographic location settings. Allowed values: "auto" to use value from fingerprint, or from one to seven comma-separated numbers for coordinates (Latitude, Longitude, Altitude, Accuracy, AltitudeAccuracy, Heading, Speed, Radius). Numbers can be skipped (e.g., "10, , 40, , 60, 70"). Note: "ignore" is not supported for this field and will cause an error.
workspaceIdNoWorkspace identifier. -1 means the default workspace.
mediaDevicesNoMedia devices settings. The allowed values are: "auto" to use value from fingerprint, "ignore" to use real values or custom location values. You can specify from one to three integer numbers that represent the following values: AudioInput, AudioOutput and VideoInput. The numbers can be skipped. For example, the following values are valid: 1,,5 - means AudioInput = 1, AudioOutput = random, VideoInput = 5
speechVoicesNoSpeech voices configuration. Allowed values: "on" to enable or "off" to disable.
proxyServerIdNoProxy server identifier (optional).
commandLineArgumentsNoCustom command line arguments to pass to the browser on startup

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the safety profile is covered. The description adds useful context beyond annotations: what a browser profile conceptually is ('a set of parameters for browser configuration ... with different fingerprints'), and that a unique identifier is returned for updating or deleting. It does not disclose any permission requirements, rate limits, or side effects of creation.

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

Conciseness3/5

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

The core action is front-loaded correctly, but the description runs to four sentences and includes a somewhat generic definitional aside ('Browser profile is a set of parameters...'). The statement 'All parameters are optional if another is not specified' is awkward and marginally wasteful.

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

Completeness3/5

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

For a 26-parameter tool with no output schema, the description partially compensates by explaining that a unique profile identifier is returned upon creation. However, it leaves significant gaps: how defaults interact across dozens of optional fingerprint fields, whether creation requires/consumes a license or proxy, and how it relates to bulk or preset-based creation are all unaddressed.

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% and every one of the 26 parameters is thoroughly documented in the schema itself, so the baseline is 3. The description only names a few example categories (screen size, hardware emulation, language, timezone, proxy) without adding syntax, defaults, or interaction rules beyond what the schema already provides.

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 states a specific verb and resource: 'creates a new browser profile in the specified workspace and the folder.' It is clear what the tool does, but it does not differentiate itself from siblings like bulk_create_profile or create_preset, which an agent could confuse with it.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative (e.g. bulk_create_profile for multiple profiles, or create_preset to reuse config). The sentence 'All parameters are optional if another is not specified' is vague and reads more like a caveat than usage guidance.

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