Skip to main content
Glama
Browser Control MCP Server

Browser Control MCP Server

by lostmind008

get_cookies

Retrieve cookies for the current page or specified URLs, optionally scoped to a tab, to inspect session state and authentication data.

Instructions

Get cookies for the current page or a specific URL

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_cookies"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlsNoURLs to get cookies for (optional)
tabIdNoTab ID (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv3.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; "Get" at least makes the read-only nature unambiguous. It does not disclose whether httpOnly/session cookies are included, what permissions or page state are required, or what happens when the URL is not currently loaded — context that matters for a browser-context read.

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?

A single, front-loaded sentence with no filler or redundancy. It is efficient, though slightly under-specified rather than maximally structured.

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?

The tool is simple and fully-optional-params, so the definition is nearly adequate. With no annotations and no output schema, the description should say something about the return shape (cookie names/values/attributes) or default behavior when urls is omitted, which it does not.

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 params (urls, tabId) are already documented. The description adds only a light hint that URL targeting is optional and defaults to the current page; it says nothing about tabId semantics or multi-URL behavior, so baseline 3 applies.

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?

States a specific verb and resource ("Get cookies") plus the scope ("current page or a specific URL"), so the agent knows exactly what it retrieves. No sibling in the catalog is cookie-related, so explicit differentiation isn't needed, but it also never mentions an alternative.

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?

The description implies two usage modes: default to the current page, or pass a URL. It gives no when-not-to-use guidance, no mention of tabId as a third targeting mode, and no prerequisites (permissions, page state).

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