Skip to main content
Glama
ifokeev

Airbrowser

by ifokeev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

manage_cookies

Inspect, clear, save, or restore browser cookies to manage login sessions and reset site state. Use get_all, clear, save, or load actions to preserve or restore session cookies between runs.

Instructions

Manage cookies for the current browser session.

Use this tool to inspect, clear, save, or restore browser cookies. Cookie management is useful for inspecting session state, preserving login sessions between browser runs, restoring previously saved sessions, or resetting website state during testing.

Args: action: - "get_all": Return all cookies currently available to the browser, including attributes such as name, value, domain, path, expiry, and security flags. - "clear": Delete all cookies from the current browser session. - "save": Save current cookies to filename. The file may be created or overwritten. - "load": Load cookies from filename into the current browser session.

filename: Filesystem path used by save/load.
    Ignored for get_all and clear.

Returns: "get_all": Current browser cookies. "clear": Confirmation that cookies were cleared. "save": Confirmation containing the destination filename. "load": Confirmation containing the source filename.

Security: Cookie data can contain authentication credentials, session identifiers, and other private information. Only inspect, save, load, or share cookies when explicitly authorized.

`filename` is passed to SeleniumBase's cookie persistence methods and
can access the filesystem available to the MCP server. Use only
trusted, authorized paths. The save action may overwrite an existing
file.

Notes: Loading saved cookies does not guarantee restoration of a login. Cookies may be expired, invalidated, domain/path restricted, or dependent on other browser state. Navigate to the relevant site when necessary so the browser has the appropriate origin for the cookies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionNoget_all
filenameNocookies.txt

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.15.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations, the description carries full responsibility for behavioral disclosure. It warns about filesystem access, potential file overwriting, privacy of cookie data, and the unreliability of restoring logins. It also clearly notes that cookies may be expired or domain-restricted, giving a transparent view of limitations.

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 well-organized into sections (Description, Args, Returns, Security, Notes) and every sentence contributes essential information. It is detailed but not redundant, balancing thoroughness with clarity.

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

Completeness5/5

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

Despite lacking an output schema, the description textually describes the return expectations for each action (e.g., confirmation containing filename). It also covers security considerations, file overwriting behavior, and functional limitations, making it complete for an agent to decide when and how to use the tool.

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

Parameters5/5

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

The schema provides no descriptions, but the tool description explains both parameters thoroughly: action with its four enum values and their effects, and filename with its purpose for save/load and that it is ignored for get_all/clear. Defaults are also mentioned implicitly. This adds significant meaning beyond the raw schema.

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 clearly states 'Manage cookies for the current browser session' and then enumerates four specific actions (get_all, clear, save, load). This is distinct from sibling tools like manage_storage or manage_window, making its purpose unambiguous.

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?

The description provides concrete usage scenarios (preserving login sessions, restoring saved sessions, resetting website state during testing) and notes about navigating to a site before loading cookies. However, it does not explicitly state when to prefer this over a sibling tool like manage_storage, so it falls short of fully explicit when/when-not guidance.

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