Skip to main content
Glama

profile_create

Creates a new browser identity with a self-consistent fingerprint frozen on creation and preserved across restarts. Define its name, engine, proxy, OS, and startup tabs.

Instructions

Create a new identity. Its fingerprint is generated and frozen on the spot.

You do not choose the fingerprint — the point of the product is that every identity gets one self-consistent, frozen set of traits that stays byte-identical across restarts. Do not create identities speculatively: they count against the installation's quota.

Args: name: the new identity's name. Must be unique — creating a name that already exists fails rather than overwriting it. engine: which browser core backs the identity. Leave unset to use this installation's default; an unknown value is rejected with the list of accepted ones. The engine field in profiles_list shows what existing identities use. proxy: exit proxy URL, e.g. "http://user:pass@host:port" or "socks5://host:port" — any vendor, bring your own. Omit it and the identity runs on a direct connection. Test a URL with proxy_check before binding it here. group, tags, note: the local ledger — which account, email, or purpose this identity is bound to. Free text, searchable in the app, and returned under meta by profiles_list. urls: startup tabs — pages opened automatically when the identity starts. force_dark: personal display preference, OFF by default. True inverts web pages that have no dark theme of their own (Google Ads and the like) to dark; sites may notice the changed colors, so use it only on identities the user manages for themselves, never on accounts being built up. Leave unset to keep pages exactly as the sites render them. Chrome-engine identities only. os: which operating system the identity presents as: "windows", "macos", "linux", "android" or "ios". Leave unset for this computer's own OS. "android" and "ios" are phone identities: Chrome engine only, and they need a recent Chrome kernel (an older one is rejected with os_needs_kernel). "ios" is simulated: it sets the browser identity, screen and touch to match an iPhone, suited to mobile web pages. mobile_model: the phone model for an "android" / "ios" identity, as an id. If you leave it unset and the OS has no default model yet, the call is rejected with mobile_model_required and the message lists the accepted ids — pick one and call again. Ignored for desktop OSes (passing it there is rejected).

Returns {name, os, created}. Fails with a readable message if the name is taken (409), if the quota is reached or the installation is unauthorized (403), or if an argument is rejected (422).

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": {
      "name": "<name>"
    },
    "name": "profile_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
osNo
nameYes
noteNo
tagsNo
urlsNo
groupNo
proxyNo
engineNo
force_darkNo
mobile_modelNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.6
    • addedInput schema / properties / mobile_model
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Mobile Model"
      +}
    • addedInput schema / properties / os
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ],
      +  "default": null,
      +  "title": "Os"
      +}
  2. First observedv0.1.5

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: uniqueness is enforced by failure rather than overwrite, quota and authorization surface as 403, invalid names/args as 409/422, and engine/os combinations fail with named codes (os_needs_kernel, mobile_model_required). It also flags the side effect that force_dark can be detected by sites and warns against using it on accounts being built up.

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?

The key concept and the anti-speculation warning are front-loaded, and the Args block is easy to scan. There is mild redundancy — the frozen/byte-identical fingerprint idea is restated in the second paragraph, and the force_dark entry runs long — but no sentence is wasted overall.

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

Completeness5/5

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

For a 10-parameter mutation tool with no annotations and no output schema, the description supplies everything needed: the return shape ({name, os, created}), the error taxonomy, the quota implication, and per-argument edge cases. Nothing an agent needs before calling it is missing.

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

Parameters5/5

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

Schema coverage is 0% with 10 parameters, yet every parameter is explained: name uniqueness semantics, engine defaulting and discovery via profiles_list, proxy URL formats with examples, the group/tags/note ledger fields and where they reappear, urls as startup tabs, force_dark's default and engine restriction, os values with the android/ios constraints, and mobile_model's conditional requirement. This fully compensates for the empty schema.

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 opening line gives a specific verb and resource ('Create a new identity') plus the defining property of the operation ('Its fingerprint is generated and frozen on the spot'). This is clearly distinguishable from every sibling (profiles_list, profile_start, profile_settings, profile_delete), none of which mint a new frozen 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 states an explicit when-not: 'Do not create identities speculatively: they count against the installation's quota.' It also routes the agent to two sibling tools at the right moments — proxy_check before binding a proxy URL, and profiles_list to discover valid engine values.

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