Skip to main content
Glama

list_identities

List persistent browser identities to retrieve profile IDs for run_task, so you can reuse warmed-up sessions with saved cookies, history, and fingerprints.

Instructions

List persistent browser identities (long-lived cookies/history/fingerprint, billed monthly). Use one in run_task via profile_id to reuse a warmed-up session — critical for sites that fingerprint cookie age, session continuity, or behavioral history (Akamai, Cloudflare-strict, DataDome).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_identities"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden, and it does disclose a real behavioral trait an agent would otherwise miss: identities are billed monthly and persist across sessions. It does not cover the return shape, pagination, or whether listing itself incurs cost, which are the remaining gaps for a zero-annotation tool.

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?

Two sentences, zero waste: the first defines the resource and its cost model, the second gives the action to take with the result. The critical framing (persistent, billed) is front-loaded.

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 parameterless listing tool with no output schema and no annotations, the description covers what is returned, what it costs, and how to use it downstream. Only the response shape and paging behavior are left unstated, which is a minor omission for a predictable list operation.

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 tool takes no parameters, so there is nothing for the description to clarify about its own input; the baseline applies. The mention of profile_id refers to a parameter of run_task, not this tool, so it adds usage context rather than parameter semantics.

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?

States a specific verb ('List') and resource ('persistent browser identities') and immediately defines what that resource contains — long-lived cookies/history/fingerprint. The persistence + monthly billing detail distinguishes it from the sibling list_browsers without needing to name it.

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

Usage Guidelines4/5

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

Gives clear when-to-use guidance: consume the returned identity in run_task via profile_id to reuse a warmed-up session, and names the exact conditions that make this worthwhile (cookie-age fingerprinting, session continuity, DataDome/Akamai/Cloudflare-strict). It does not state when NOT to use this rather than list_browsers or start_browser, so it stops short of full alternative routing.

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