Skip to main content
Glama

browser_unselect_checkbox

Unselect a checkbox in a web browser by specifying a locator strategy and value, enabling automation of form interactions and UI testing.

Instructions

Unselect a checkbox

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
byYesLocator strategy to find element
valueYesValue for the locator strategy
timeoutNoMaximum time to wait for element in milliseconds

Implementation Reference

  • Handler function for the browser_unselect_checkbox tool, which locates the checkbox using ActionService and unselects it if selected.
    server.tool('browser_unselect_checkbox', 'Unselect a checkbox', { ...locatorSchema }, async ({ by, value }) => {
      try {
        const driver = stateManager.getDriver();
        const actionService = new ActionService(driver);
        await actionService.unselectCheckbox({ by, value });
        return {
          content: [{ type: 'text', text: `Unselected checkbox` }],
        };
      } catch (e) {
        return {
          content: [
            {
              type: 'text',
              text: `Error unselecting checkbox: ${(e as Error).message}`,
            },
          ],
        };
      }
    });
  • Core implementation of unselecting a checkbox: waits for the element, checks if selected, and clicks to toggle off.
    async unselectCheckbox(params: LocatorParams): Promise<void> {
      const locator = LocatorFactory.createLocator(params.by, params.value);
      const checkbox = await this.driver.wait(until.elementLocated(locator), params.timeout || 15000);
      if (await checkbox.isSelected()) {
        await checkbox.click();
      }
    }
  • Zod schema definition for locator parameters (by, value, timeout) used in the tool input.
    export const locatorSchema = {
      by: z
        .enum(['id', 'css', 'xpath', 'name', 'tag', 'class', 'link', 'partialLink'])
        .describe('Locator strategy to find element'),
      value: z.string().describe('Value for the locator strategy'),
      timeout: z.number().optional().describe('Maximum time to wait for element in milliseconds'),
    };
Behavior2/5

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

With no annotations provided, the description carries full burden but only states the basic action without disclosing behavioral traits. It doesn't mention that this likely requires the checkbox to be selected first, potential side effects, error conditions, or interaction patterns, leaving significant gaps for a mutation tool.

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?

The description is a single, efficient sentence with zero wasted words. It's appropriately sized for a simple action and front-loaded with the essential information, making it easy to parse quickly.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks information about what happens after unselecting (e.g., state changes, return values), error handling, and interaction with the checkbox's initial state, which are crucial for proper usage.

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 schema fully documents all three parameters (by, value, timeout). The description adds no additional parameter semantics beyond what's already in the structured schema, meeting the baseline for high coverage.

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 'Unselect a checkbox' clearly states the action (unselect) and target resource (checkbox), making the purpose immediately understandable. However, it doesn't differentiate from its sibling 'browser_select_checkbox' beyond the opposite action, missing explicit comparison that would warrant a perfect score.

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 is provided on when to use this tool versus alternatives like 'browser_click' for toggling checkboxes or 'browser_select_checkbox' for the opposite action. The description assumes context without explaining prerequisites or appropriate scenarios.

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/pshivapr/selenium-mcp'

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