Skip to main content
Glama

click

Automate clicks on web page elements using CSS selectors to test consent management platforms and browser interactions in the Autoconsent MCP server environment.

Instructions

Click elements on the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYesCSS selector for element to click

Implementation Reference

  • The switch case in handleToolCall that implements the 'click' tool by calling page.click on the given CSS selector, with success/error response handling.
    case "click":
      try {
        await page.click(args.selector);
        return {
          content: [
            {
              type: "text",
              text: `Clicked: ${args.selector}`,
            },
          ],
          isError: false,
        };
      } catch (error) {
        return {
          content: [
            {
              type: "text",
              text: `Failed to click ${args.selector}: ${(error as Error).message}`,
            },
          ],
          isError: true,
        };
      }
  • src/index.ts:65-78 (registration)
    Registration of the 'click' tool in the TOOLS array, including name, description, and input schema definition.
    {
      name: "click",
      description: "Click elements on the page",
      inputSchema: {
        type: "object",
        properties: {
          selector: {
            type: "string",
            description: "CSS selector for element to click",
          },
        },
        required: ["selector"],
      },
    },
  • Input schema for the 'click' tool, defining the required 'selector' parameter.
    inputSchema: {
      type: "object",
      properties: {
        selector: {
          type: "string",
          description: "CSS selector for element to click",
        },
      },
      required: ["selector"],
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('click elements') but doesn't describe what happens after clicking (e.g., page navigation, event triggers, error handling), or any constraints like rate limits or permissions needed. This leaves significant gaps in understanding the tool's behavior.

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 extremely concise with a single, direct sentence ('Click elements on the page') that front-loads the core action. There is no wasted verbiage, making it efficient and easy to parse.

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?

Given the tool's complexity (interactive action on web elements) and lack of annotations or output schema, the description is insufficient. It doesn't cover behavioral outcomes, error cases, or integration with sibling tools like 'navigate', leaving the agent with incomplete context for effective use.

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?

The input schema has 100% description coverage, clearly documenting the 'selector' parameter as a CSS selector. The description doesn't add any extra meaning beyond this, such as examples or constraints on selectors, so it meets the baseline for high schema coverage without compensating further.

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 verb ('click') and resource ('elements on the page'), making the purpose immediately understandable. However, it doesn't distinguish this tool from potential sibling interactions like 'select' or 'test_rule', which might also involve element interaction.

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?

The description provides no guidance on when to use this tool versus alternatives like 'select' or 'test_rule', nor does it mention prerequisites such as needing a page to be loaded first. It lacks explicit context or exclusions for usage.

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/noisysocks/autoconsent-mcp'

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