Skip to main content
Glama

playwright_iframe_click

Click elements within iframes on web pages using CSS selectors for both the iframe and the target element. Enables precise browser automation for interacting with embedded 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 the 'playwright_iframe_click' tool. Uses Playwright's frameLocator to locate the iframe and click the specified element inside it.
    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 input/output schema definition for the tool, specifying parameters iframeSelector and selector.
    {
      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"],
      },
    },
  • Dispatch registration in the main tool handler switch statement, routing calls to the IframeClickTool instance.
    case "playwright_click":
      return await clickTool.execute(args, context);
      
    case "playwright_iframe_click":
      return await iframeClickTool.execute(args, context);
  • src/index.ts:22-27 (registration)
    Registers all tools (including schema for playwright_iframe_click) with the MCP server via createToolDefinitions() and setupRequestHandlers.
    // Create tool definitions
    const TOOLS = createToolDefinitions();
    
    // Setup request handlers
    setupRequestHandlers(server, TOOLS);
  • src/tools.ts:453-454 (registration)
    Includes 'playwright_iframe_click' in the BROWSER_TOOLS array used for conditional browser launching.
    "playwright_click",
    "playwright_iframe_click",
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 offers minimal behavioral insight. It states the action ('click') but doesn't disclose whether this might trigger page navigation, open new tabs, require element visibility, have timing delays, or handle errors. For a UI automation tool with zero annotation coverage, this leaves critical behavioral traits unspecified.

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 function without unnecessary words. It's front-loaded with the core action and context, making it easy to parse quickly. Every word earns its place in conveying the essential purpose.

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 complexity of UI automation (interacting with iframes, potential side effects) and lack of annotations or output schema, the description is insufficiently complete. It doesn't address what happens after the click (e.g., page changes, return values, error conditions), nor does it provide behavioral context needed for safe and effective use in an automated testing scenario.

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 clearly documented in the schema ('iframeSelector' and 'selector'). The description adds no additional parameter semantics beyond implying these selectors target iframes and elements within them, which is already evident from parameter names and schema descriptions. Baseline 3 is appropriate when 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 ('an element in an iframe on the page'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'playwright_click' (which clicks elements without iframe context) or 'playwright_iframe_fill' (which fills iframe elements), missing full sibling differentiation.

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

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

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

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