Skip to main content
Glama
mcp-browserdata

mcp-browserdata

by igortetyuev

get_cookies

Retrieve cookies from an installed browser, optionally filtered by domain suffix, with cookie values masked unless explicitly revealed.

Instructions

Cookies for a browser, optionally filtered by domain suffix. Without reveal=True the value field is masked.

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": {
      "browser": "<browser>"
    },
    "name": "get_cookies"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainNo
revealNo
browserYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the single most important behavioral trait: values are masked unless reveal=True, which materially changes what the caller receives. It leaves other behavior unstated, such as whether it reads a live browser session or a stored profile, and any permission requirements.

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 short sentences, front-loaded with purpose and scope, followed by the one non-obvious caveat about masking. Nothing is repeated from the schema and no sentence is padding.

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?

An output schema exists, so return shape needn't be explained, and the masking caveat covers the main surprise for a credential-adjacent read. Still, for a three-parameter tool with zero annotation and zero schema-description coverage, the unexplained browser argument and missing access prerequisites leave real gaps.

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 coverage is 0%, so the description must compensate, and it does for two of three parameters: it clarifies that domain matches by suffix (not exact match) and that reveal controls value masking rather than selection. The required browser parameter receives no explanation of expected format (name vs. id) despite being the only required field.

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 names the resource (cookies), the scoping unit (a browser), and an optional filter (domain suffix), which is enough to tell it apart from set_cookies and from storage/credential siblings. It falls short of 5 only because it is phrased as a noun fragment with no explicit retrieval verb.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the agent can infer you call this to read cookies for one browser, optionally narrowed by domain. There is no guidance on when to prefer this over get_site_storage or get_credentials, and no prerequisites are mentioned (e.g. whether the browser must be running).

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