Skip to main content
Glama
Sign In
GoLogin MCP

GoLogin MCP

Official
by gologinapp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_profile__id__web

Remove a specified browser profile from the cloud using its unique ID. This action stops and deletes the profile, allowing for efficient management of GoLogin browser environments.

Instructions

Stop profile in the cloud

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden. 'Stop' implies a mutation, but it doesn't disclose if this is destructive, reversible, requires permissions, or has side effects. For a tool with no annotations and a vague action, this is a significant gap in behavioral context.

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 description is a single, short sentence with no wasted words, making it front-loaded and easy to parse. However, its brevity contributes to under-specification rather than clarity.

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 tool with no annotations, 0% schema coverage, no output schema, and a vague purpose, the description is incomplete. It fails to compensate for the lack of structured data, leaving the agent with insufficient information to use the tool effectively.

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

Parameters2/5

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

Schema description coverage is 0%, and the description adds no parameter information. It doesn't explain what 'id' represents or its format, leaving the single required parameter undocumented beyond its type in the schema.

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

Purpose3/5

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

The description 'Stop profile in the cloud' uses a verb ('Stop') and resource ('profile'), but it's vague about what 'Stop' means—does it delete, deactivate, or pause? It doesn't distinguish from siblings like 'delete_profile' or 'delete_profile__id__web' (which appears to be a duplicate name issue), leaving ambiguity in its specific function.

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. With siblings like 'delete_profile' and 'delete_profile__id__web' (potentially similar), there's no indication of differences, prerequisites, or exclusions, leaving the agent to guess based on context alone.

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