Retrieve all cookies for the current page by providing the session ID from browser_navigate. Inspect authentication or session state during web scraping.
Get all cookies for the current page.
| Name | Required | Description | Default |
|---|---|---|---|
| session_id | Yes | Session ID returned by browser_navigate |
Changes observed during successful MCP inspections.
v2.7.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds the scope of the read ('all cookies, current page') but says nothing about cookie scope semantics (domain vs page), httpOnly inclusion, or output format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single short sentence with the verb and scope front-loaded and no filler. Nothing could be removed without losing meaning.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read tool with full parameter coverage and complete safety annotations, this is close to adequate, but the absence of an output schema means the description should say what is returned (name/value pairs, count, format) and whether the scope is page or domain. The 'current page' framing may mislead on cookie scope.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The sole parameter session_id is fully documented in the schema (100% coverage) as coming from browser_navigate, so the schema already carries the semantics. The description adds no parameter-level detail, which is the expected baseline when schema coverage is complete.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Get) and resource (cookies) with a scope qualifier (current page), so it is clearly separable from browser_set_cookies and browser_clear_cookies by verb. The phrase 'current page' is slightly imprecise since cookies are domain-scoped, but the intent is unambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this versus alternatives such as browser_local_storage, browser_set_cookies, or reading cookies inside browser_evaluate. No prerequisites or context selection criteria are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.