Skip to main content
Glama

session_set_cookie

Set browser cookies with custom name, value, domain, path, and security flags to manage sessions during automated browser testing and security assessments.

Instructions

Set a cookie in the browser

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCookie name
valueYesCookie value
domainNoCookie domain
pathNoCookie path/
secureNoSecure flag
http_onlyNoHttpOnly flag
Behavior2/5

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

With no annotations, the description should disclose behaviors like overwriting existing cookies or domain restrictions. It only says 'Set a cookie', leaving important traits undocumented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise at 6 words, but lacks necessary context. It is not verbose, but trades completeness for brevity.

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 6 parameters and no output schema, the description is incomplete. It does not explain return values, side effects, or interaction with other session tools.

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 100%, so the baseline is 3. The description adds no meaning beyond the schema, which adequately documents all parameters.

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 'Set a cookie in the browser' clearly states the action and resource. It differentiates from siblings like session_get_cookie (get vs set) but could be more specific about create/update behavior.

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 guidance on when to use this tool versus alternatives like session_delete_cookie or session_clear_cookies. The description does not provide context or prerequisites.

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/D4D25A/PyPen'

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