Skip to main content
Glama

pilot_set_cookie

Set cookies on web pages to manage sessions, store user preferences, or test authentication flows during browser automation.

Instructions

Set a cookie on the current page domain.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesCookie name
valueYesCookie value

Implementation Reference

  • The handler for 'pilot_set_cookie' is registered and implemented within 'registerSettingsTools' in 'src/tools/settings.ts'. It uses the 'BrowserManager' to add a cookie to the current page's domain.
    server.tool(
      'pilot_set_cookie',
      'Set a cookie on the current page domain.',
      {
        name: z.string().describe('Cookie name'),
        value: z.string().describe('Cookie value'),
      },
      async ({ name, value }) => {
        await bm.ensureBrowser();
        try {
          const page = bm.getPage();
          const url = new URL(page.url());
          await page.context().addCookies([{
            name,
            value,
            domain: url.hostname,
            path: '/',
          }]);
          return { content: [{ type: 'text' as const, text: `Cookie set: ${name}=****` }] };
        } catch (err) {
          return { content: [{ type: 'text' as const, text: wrapError(err) }], isError: true };
        }
      }
    );
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. It only specifies scope ('current page domain') but fails to mention overwrite behavior, cookie persistence, security restrictions, or that this is a state-mutating operation with side effects on subsequent requests.

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?

Seven words in a single sentence with the action front-loaded ('Set'). No redundant text or noise.

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

Completeness3/5

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

Adequate minimum for a simple two-parameter tool, but lacks important behavioral context (prerequisites, overwrite semantics) that would be necessary for safe execution in a browser automation context.

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?

Input schema has 100% description coverage ('Cookie name', 'Cookie value'). The description adds no additional semantic context beyond the schema, earning the baseline score for high-coverage schemas.

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?

Clear verb ('Set') and resource ('cookie') with specific scope ('current page domain'). However, it does not explicitly distinguish from sibling tool pilot_import_cookies (likely for bulk operations) or clarify whether this creates new or updates existing cookies.

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?

Provides no guidance on when to use this single-cookie setter versus pilot_import_cookies, nor mentions prerequisites such as needing to navigate to the domain first before setting cookies.

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/TacosyHorchata/Pilot'

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