WaveXisMCP

wavexis_cookies_set

Set a browser cookie for the current page by specifying name, value, domain, and optional URL. Fixes missing or incorrect cookies to manage sessions, preferences, or authentication states.

Instructions

Set a single cookie in the browser for the current page.

Use wavexis_cookies_get to read cookies, or wavexis_cookies_delete to remove a specific cookie.

Side effects: launches/acquires a browser backend, navigates to url if provided, mutates browser cookie state. Returns: JSON string with keys: 'status' ('ok'/'error').

Input Schema

TableJSON Schema

Name	Required	Description	Default
`input`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed20 schema fields changedv1.6.24Jul 29, 2026
- addedInput schema / $defs / CookiesSetInput / properties / backend / description
```
Added value: +"Backend: 'cdp', 'bidi', or 'auto'"
```
- addedInput schema / $defs / CookiesSetInput / properties / backend / enum
```
Added value: +[
+  "cdp",
+  "bidi",
+  "auto"
+]
```
- addedInput schema / $defs / CookiesSetInput / properties / domain / description
```
Added value: +"Cookie domain"
```
- addedInput schema / $defs / CookiesSetInput / properties / domain / minLength
```
Added value: +1
```
- addedInput schema / $defs / CookiesSetInput / properties / headless / description
```
Added value: +"Run browser in headless mode"
```
- addedInput schema / $defs / CookiesSetInput / properties / http_only / description
```
Added value: +"Whether the cookie is HttpOnly"
```
- addedInput schema / $defs / CookiesSetInput / properties / name / description
```
Added value: +"Name of the item"
```
- addedInput schema / $defs / CookiesSetInput / properties / name / minLength
```
Added value: +1
```
- addedInput schema / $defs / CookiesSetInput / properties / path / description
```
Added value: +"Cookie path"
```
- addedInput schema / $defs / CookiesSetInput / properties / path / minLength
```
Added value: +1
```
- addedInput schema / $defs / CookiesSetInput / properties / same_site / description
```
Added value: +"SameSite attribute: Strict, Lax, or None"
```
- addedInput schema / $defs / CookiesSetInput / properties / same_site / enum
```
Added value: +[
+  "Strict",
+  "Lax",
+  "None"
+]
```
- addedInput schema / $defs / CookiesSetInput / properties / secure / description
```
Added value: +"Whether the cookie is Secure"
```
- addedInput schema / $defs / CookiesSetInput / properties / session_id / description
```
Added value: +"Active session ID. If omitted, a stateless session is created for this call."
```
- addedInput schema / $defs / CookiesSetInput / properties / url / description
```
Added value: +"URL to navigate to (required without session_id)"
```
- addedInput schema / $defs / CookiesSetInput / properties / value / description
```
Added value: +"Value to set"
```
- addedInput schema / $defs / CookiesSetInput / properties / value / minLength
```
Added value: +1
```
- addedInput schema / $defs / CookiesSetInput / properties / wait_timeout / description
```
Added value: +"Timeout in ms for wait conditions"
```
- addedInput schema / $defs / CookiesSetInput / properties / wait_timeout / maximum
```
Added value: +300000
```
- addedInput schema / $defs / CookiesSetInput / properties / wait_timeout / minimum
```
Added value: +1000
```
First observedv1.0.1Jul 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond annotations (readOnlyHint=false, etc.), the description details side effects: launches/acquires browser backend, navigates to url if provided, mutates cookie state. Return format is also specified.

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 concise sentences with front-loaded purpose, minimal waste. Every sentence adds value.

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?

Covers purpose, side effects, return, and sibling tools. Could mention session_id or prerequisites, but given the tool's simplicity and sibling context, it is sufficiently complete.

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?

The description does not repeat parameter details, but the schema already has descriptions for all parameters (high coverage). It adds value by noting that 'url' triggers navigation, which complements the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it sets a single cookie for the current page, distinguishes from sibling tools (get and delete), and mentions side effects like navigation and mutation.

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 description explicitly mentions alternative tools for reading and deleting cookies, providing clear when-to-use guidance. It could be stronger by adding when not to use 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

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

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/MathiasPaulenko/wavexis-mcp'

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