Skip to main content
Glama
Sign In
GoLogin MCP

GoLogin MCP

Official
by gologinapp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_profile

Remove multiple browser profiles in bulk by specifying their IDs. This tool simplifies profile management within the GoLogin MCP server, enabling efficient cleanup of unused or outdated profiles.

Instructions

Delete multiple profiles

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

Input Schema

NameRequiredDescriptionDefault
profilesToDeleteYesArray of profile IDs that you want to delete.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries full burden but only states the action without behavioral details. It doesn't disclose if deletion is permanent, reversible (though 'get_deleted_profiles_v2' and 'post_deleted_profiles_restore' hint at recovery), requires specific permissions, or has side effects like cascading deletions.

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 a single, efficient sentence with zero wasted words. It is front-loaded with the core action and resource, making it immediately understandable without unnecessary elaboration.

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

Completeness2/5

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

For a destructive mutation tool with no annotations and no output schema, the description is inadequate. It lacks critical context such as permanence, permissions, error handling, or return values, leaving significant gaps for safe and effective use by an AI agent.

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%, with the parameter 'profilesToDelete' well-documented as an array of profile IDs. The description adds no additional parameter semantics beyond implying batch deletion through 'multiple profiles', which aligns with the array type but doesn't provide extra value over the schema.

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 'Delete multiple profiles' clearly states the action (delete) and resource (profiles), with 'multiple' indicating batch capability. It distinguishes from single-delete siblings like 'delete_profile__id__web' by specifying multiplicity, though it doesn't explicitly name alternatives.

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?

No guidance is provided on when to use this tool versus alternatives like 'delete_profile__id__web' for single deletions or 'delete_workspaces__wid__profiles' for workspace-level deletions. The description lacks context about prerequisites, permissions, or recovery options.

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

Related Tools