Skip to main content
Glama
Sign In
dolphin-anty-mcp

dolphin-anty-mcp

by someorgyouwontcareabout
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Bulk create browser profiles

create_profiles_bulk

Create multiple browser profiles in a single API call. Supply shared settings once and override per profile to save time when setting up Dolphin Anty environments.

Instructions

Create many profiles in one call. Important: unlike create_profile, the backend IGNORES a nested fingerprint object here — fingerprint data must be supplied as flattened top-level keys (useragent, uaFullVersion, screenWidth, screenHeight, cpu, memory, connectionRtt, webglInfo, …). Use common for values shared by every item; per-item values win on conflict.

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

Input Schema

NameRequiredDescriptionDefault
itemsYesProfile definitions. Each needs at least name, platform, browserType, platformVersion.
commonNoFields merged into every item before validation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

The description discloses the critical behavior that the backend ignores a nested 'fingerprint' object and requires flattened top-level keys, which is not apparent from the annotations or schema. It also explains the merging semantics between 'common' and per-item values. While it does not mention error handling or side effects, the disclosed behaviors are significant and exceed what annotations already provide.

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 two sentences, front-loaded with the main purpose, and immediately followed by the most important caveat. Every sentence earns its place, condensing significant detail (flattened key list, merge precedence, contrast with sibling) into a compact, scannable format.

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?

For a bulk creation tool with open-ended schemas (additionalProperties: true) and no output schema, the description is fairly complete: it explains the main gotcha (flattened fingerprint keys), the 'common' merge mechanism, and provides a partial list of valid keys. It lacks information about request limits, validation errors, or response format, but these are partially covered by the absence of output schema and the open-world hint, making the description adequate for proper usage.

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 schema descriptions cover 100% of parameters, providing baseline meaning for 'items' and 'common'. The description adds semantic value by elaborating on the 'common' merge behavior and specifying that fingerprint data must be flattened top-level keys, which is beyond the schema's generic 'additionalProperties' allowance. This helps the agent understand the intended structure more precisely.

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 states 'Create many profiles in one call' which clearly identifies the action (create), the resource (profiles), and the bulk nature. It explicitly contrasts with 'create_profile' by highlighting the fingerprint nesting difference, thus distinguishing it from the sibling tool.

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?

The description explicitly names the alternative tool (create_profile) and explains a critical difference in how fingerprint data must be supplied, guiding the user to this tool for bulk creation. It also provides usage guidance on using 'common' for shared values and the precedence rule, which helps decide when to use this tool and how to structure input.

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