Skip to main content
Glama

playwright_iframe_click

Click elements within iframes during browser automation by specifying both iframe and element selectors to interact with nested page content.

Instructions

Click an element in an iframe on the page

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
iframeSelectorYesCSS selector for the iframe containing the element to click
selectorYesCSS selector for the element to click

Implementation Reference

  • The core handler implementation for 'playwright_iframe_click' in the IframeClickTool class. It locates the iframe using frameLocator, checks if it exists, clicks the specified element inside it, and returns a success message.
    export class IframeClickTool extends BrowserToolBase {
      /**
       * Execute the iframe click tool
       */
      async execute(args: any, context: ToolContext): Promise<ToolResponse> {
        return this.safeExecute(context, async (page) => {
          const frame = page.frameLocator(args.iframeSelector);
          if (!frame) {
            return createErrorResponse(`Iframe not found: ${args.iframeSelector}`);
          }
    
          await frame.locator(args.selector).click();
          return createSuccessResponse(`Clicked element ${args.selector} inside iframe ${args.iframeSelector}`);
        });
      }
  • The tool definition including name, description, and input schema (iframeSelector and selector required) for 'playwright_iframe_click'.
    {
      name: "playwright_iframe_click",
      description: "Click an element in an iframe on the page",
      inputSchema: {
        type: "object",
        properties: {
          iframeSelector: {
            type: "string",
            description: "CSS selector for the iframe containing the element to click",
          },
          selector: { type: "string", description: "CSS selector for the element to click" },
        },
        required: ["iframeSelector", "selector"],
      },
    },
  • Instantiation of the IframeClickTool instance in the initializeTools function.
    if (!iframeClickTool) iframeClickTool = new IframeClickTool(server);
  • The switch case in handleToolCall function that dispatches 'playwright_iframe_click' calls to the iframeClickTool's execute method.
    return await iframeClickTool.execute(args, context);
  • Type declaration for the iframeClickTool instance variable.
    let iframeClickTool: IframeClickTool;
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') but doesn't describe what happens after clicking (e.g., page navigation, element state changes, error handling), whether it waits for elements to be visible, or any side effects. For a UI interaction tool with zero annotation coverage, this leaves significant behavioral gaps.

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 that directly states the tool's purpose with zero wasted words. It's appropriately sized for a simple action tool and front-loaded with the core functionality.

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?

Given the tool's moderate complexity (interacting with iframes), no annotations, and no output schema, the description is minimally adequate but incomplete. It covers the basic action but lacks context about behavioral outcomes, error conditions, or relationship to sibling tools, which would help an agent use it correctly.

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%, with both parameters ('iframeSelector' and 'selector') clearly documented in the schema. The description doesn't add any additional meaning beyond what the schema provides (e.g., no examples of selector syntax, no context about nested iframes). Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('click') and target ('element in an iframe on the page'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'playwright_click' (which clicks elements not in iframes) or 'playwright_iframe_fill' (which fills iframe elements), though the 'iframe' prefix in the name provides some implicit distinction.

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. The description doesn't mention when to choose this over 'playwright_click' (for non-iframe elements) or 'playwright_iframe_fill' (for filling iframe elements instead of clicking), nor does it specify prerequisites like needing an iframe context or page navigation state.

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/aakashH242/mcp-playwright'

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