Skip to main content
Glama

Create a browser profile

create_profile

Create a new browser profile with a coherent fingerprint to avoid detection. Add proxy or custom fingerprint when needed.

Instructions

Create a NEW browser profile. If the user named a profile and asked you to open, run or 'spin up' it, that is start_profile with name — not this tool. Creating a lookalike loses every cookie, login and bit of history the real one holds. This tool refuses a name that already exists unless allowDuplicateName is set.

By default this pulls a real, internally coherent fingerprint from the Dolphin dataset and applies it — which is what you want, since Dolphin does NOT generate fingerprints server-side and an incoherent one defeats the point of an anti-detect browser. The fingerprint is flattened into the profile's own field shape (useragent/cpu/memory/webglInfo as {mode,value} objects); handing the API a nested fingerprint object as its docs suggest produces a profile that cannot be read or started. Pass fingerprint from get_fingerprint to choose one yourself, or set autoFingerprint: false to create a bare profile.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
argsNoCustom Chromium launch arguments, e.g. ["disable-gpu"].
nameYes
tagsNoFree-form tags.
notesNoFree-form note objects.
proxyNoProxy for the profile. Either `{ id }` to attach an existing proxy, or `{ type, host, port, ... }` to create a new one and attach it. Omit for no proxy.
folderIdNo
platformYesHost OS the profile mimics.
statusIdNo
fingerprintNoA full fingerprint object from `get_fingerprint`, used verbatim.
mainWebsiteNoMain website — affects the profile icon and some spoofing tweaks.
browserVersionNoMajor Chrome version to imitate, e.g. 138. Only used when auto-fetching a fingerprint.
autoFingerprintNoFetch a coherent fingerprint automatically when none is supplied.
platformVersionNoOS version. Taken from the fingerprint when omitted.
allowDuplicateNameNoPermit creating a second profile with a name that already exists. Off by default, because a name collision almost always means the intended profile already exists.
Behavior5/5

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

The description reveals several critical behaviors beyond annotations: default auto-fetching of a coherent Dolphin fingerprint, refusal of duplicate names unless allowDuplicateName is true, and the serious pitfall that a nested fingerprint object produces a profile that cannot be read or started. This is valuable context that prevents misuse.

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 long but every sentence earns its place. It is front-loaded with purpose, then differences from siblings, then critical warnings and implementation details. Nothing is redundant and the structure flows logically.

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

Completeness4/5

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

The description covers the tool's core purpose, sibling differentiation, duplicate-name handling, and the fingerprint shape trap in depth. It does not explicitly mention return values or that the created profile is not automatically started, but given the detailed schema and the presence of separate start tools, this is nearly complete.

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

Parameters4/5

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

The description adds deep meaning for key parameters: fingerprint must be flattened into the profile's field shape, browserVersion only matters when auto-fetching, and allowDuplicateName prevents unintended duplicates. Schema coverage is 79% and these insights go beyond the schema's descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Create a NEW browser profile' with a specific verb and resource. It also explicitly distinguishes itself from start_profile, which opens/runs an existing profile.

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

Usage Guidelines5/5

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

It gives explicit when-not guidance: if the user wants to open/run/spin up a named profile, that is start_profile, not this tool. It also warns about data loss when creating a lookalike and suggests alternatives like passing a fingerprint from get_fingerprint or setting autoFingerprint to false.

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/someorgyouwontcareabout/DolphinMCP'

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