Skip to main content
Glama
InDate
by InDate

storage

Access and manage browser storage including cookies, localStorage, and sessionStorage. Perform actions like get, set, or clear storage data.

Instructions

Access and manage browser storage (cookies, localStorage, sessionStorage). Actions: getCookies (get cookies), setCookie (set cookie), getLocalStorage (get localStorage), setLocalStorage (set localStorage), clear (clear storage)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNolocalStorage key (optional for getLocalStorage, required for setLocalStorage)
urlNoURL to get cookies for (optional for getCookies action)
nameNoCookie name (required for setCookie action)
pathNoCookie path (optional for setCookie action)
typesNoStorage types to clear (for clear action, default: all)
valueNoCookie/storage value (required for setCookie and setLocalStorage actions)
actionYesStorage action: getCookies (get cookies), setCookie (set cookie), getLocalStorage (get localStorage), setLocalStorage (set localStorage), clear (clear storage)
domainNoCookie domain (optional for setCookie action)
reasonNoWhy storage needs to be cleared (required for clear action)
secureNoSecure cookie (optional for setCookie action, default: false)
expiresNoCookie expiration timestamp (optional for setCookie action)
httpOnlyNoHTTP only cookie (optional for setCookie action, default: false)
connectionReasonNoConnection reference (use the reference from launchChrome output, e.g., "unnamed-connection-default" or your renamed tab)
Behavior2/5

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

No annotations are present, so the description must carry the full burden. It mentions 'Access and manage', implying both read and write, but fails to disclose that 'clear' is destructive and requires a reason. No mention of permissions, rate limits, or side effects beyond the action names. Minimal transparency.

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?

The description is a single, well-structured sentence with a parenthetical list. It is concise but slightly repetitive (e.g., 'getCookies (get cookies)'). Still efficient for a multi-action tool.

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

Completeness2/5

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

For a tool with 13 parameters and 5 actions, the description omits critical information like return values, side effects of each action, and usage context (e.g., when to use 'clear' vs individual actions). No output schema exists, so the description should compensate, but 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 the baseline is 3. The description adds little beyond the schema: it only repeats the action enum values with parenthetical explanations. No additional context about parameter interdependencies or formatting is provided.

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 clearly states the tool's purpose: 'Access and manage browser storage' and lists the specific actions. However, it does not differentiate from sibling tools like 'network' or 'console' beyond the obvious domain, and the actions are listed but not described in a way that highlights their distinct purposes. The verb 'manage' is somewhat broad.

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

Usage Guidelines2/5

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

No usage guidelines are provided. The description does not specify when to use this tool over siblings, nor does it offer guidance on selecting among the five actions. The agent must rely solely on parameter enums and names, which is insufficient for effective decision-making.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/InDate/cdp-tools-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server