Skip to main content
Glama
mcp-browserdata

mcp-browserdata

by igortetyuev

set_cookies

Writes specified cookies into a browser's cookie jar on explicit request, enabling controlled cookie setup for browser sessions.

Instructions

Write cookies into a browser's jar. ONLY on explicit user request. Each item: {name, value, domain, path?, expires?, secure?, http_only?, same_site?}.

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>",
      "cookies": "<cookies>"
    },
    "name": "set_cookies"
  }
}

Input Schema

NameRequiredDescriptionDefault
browserYes
cookiesYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full burden: it signals a write mutation and adds a consent constraint, which is valuable. However, it never says whether an existing cookie with the same name/domain is overwritten or merged, whether the write persists across sessions, or what happens on partial failure — all material for a cookie-jar mutation.

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?

Three short sentences, front-loaded with the action, then the safety gate, then the payload shape. No filler or restated title, and every clause contributes.

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

Completeness4/5

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

For a two-parameter tool with an output schema (so return values needn't be described), the description covers the action, the consent requirement, and the full item shape. The remaining gap is overwrite/merge semantics and the format of the 'browser' argument.

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

Parameters4/5

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

Schema coverage is 0% and the items schema is an untyped object with additionalProperties, so the description's field list (name, value, domain, plus optional path, expires, secure, http_only, same_site) supplies nearly all the meaning an agent needs for the cookies array. The 'browser' parameter is left unexplained, which keeps it from a 5.

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: 'Write cookies into a browser's jar.' The verb 'write' clearly distinguishes it from the read-oriented sibling get_cookies without needing to name it. It stops short of a 5 only because it doesn't explicitly scope what read-side tools cover.

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 line 'ONLY on explicit user request' gives a firm when-to-use gate, which is unusually clear for a mutation tool. It doesn't name a preferred alternative path or describe prerequisites, so it falls short of explicit when/when-not/alternatives routing.

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