Skip to main content
Glama
Sign In
ZennoBrowser MCP Server

ZennoBrowser MCP Server

Official
by ZennoLab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Deletes a proxy from the list by its identifier.

delete_proxy
DestructiveIdempotent

Deletes an existing proxy from a workspace by its unique ID, removing it from the proxy list to keep browser settings current.

Instructions

This method deletes a proxy from the list by the specified ID. The proxyId value must match an existing proxy in the specified workspace.

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

Input Schema

NameRequiredDescriptionDefault
proxyIdYesUnique identifier of the proxy to delete (required).
workspaceIdNoWorkspace identifier. -1 means the default workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds the precondition that the ID must match an existing proxy in the given workspace, which is useful context, but it says nothing about failure behavior or what happens to profiles bound to the deleted proxy.

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?

Two short sentences that are front-loaded with the action and scope. It is slightly redundant, restating the 'by the specified ID' idea from the title, but nothing is padded or buried.

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

Completeness3/5

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

For a destructive delete tool with annotations covering safety and no output schema, the description is adequate: it names the resource, the key parameter, and the existence precondition. It stops short of covering side effects (e.g., effect on profiles referencing the proxy) or error behavior, which a delete operation would benefit from.

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%, so both parameters are already documented, establishing the baseline of 3. The description's note that proxyId must exist in the specified workspace adds mild semantic value about the workspaceId relationship but no syntax or format detail beyond 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 states a specific verb and resource ('deletes a proxy from the list by the specified ID'), so the operation is unambiguous. It does not, however, explicitly differentiate itself from the closely named sibling bulk_delete_proxy, leaving the agent to infer singular vs. bulk from the name alone.

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?

The description offers no when-to-use guidance or alternatives, even though bulk_delete_proxy and delete_proxy_folder sit in the same sibling set. The stated precondition ('must match an existing proxy') is a constraint, not usage routing.

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