Bright Data MCP: when the agent begs for JavaScript, filter the snapshot first

Bright Data MCP: when the agent begs for JavaScript, filter the snapshot first

TL;DR

Two takeaways: 1. If your agent keeps asking for direct JavaScript execution against pages, upgrade to MCP v2.8.1 or later, which added the evaluate-JavaScript style tools the reporter asked for. Before reaching for script execution, re-fetch the ARIA snapshot with filters; an unclear snapshot often resolves into a usable one and keeps the interaction in the supported click/type toolset (which already covers form filling).

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

2. 3. When requesting new tools, show the maintainer the exact agent behavior (the reporter's pasted agent quote is what made the case).

Context: GitHub issue (brightdata/brightdata-mcp#91, closed): a feature request for additional browser tools. The reporter found their agent (Claude Sonnet 4.5) asking for an evaluate-arbitrary-JavaScript tool when the ARIA snapshot was not clear enough to locate an element. The maintainer shipped the new tools in MCP v2.8.1 for both versions, and the reporter confirmed. The thread also carries a practical tip: when the ARIA snapshot is not clear, fetch it again with filters before giving up on the element.

Source: GitHub issue (brightdata/brightdata-mcp#91, closed): a feature request for additional browser tools. The reporter found their agent (Claude Sonnet 4.5) asking for an evaluate-arbitrary-JavaScript tool when the ARIA snapshot was not clear enough to locate an element. The maintainer shipped the new tools in MCP v2.8.1 for both versions, and the reporter confirmed. The thread also carries a practical tip: when the ARIA snapshot is not clear, fetch it again with filters before giving up on the element.

Verified resolution: Two takeaways: 1. If your agent keeps asking for direct JavaScript execution against pages, upgrade to MCP v2.8.1 or later, which added the evaluate-JavaScript style tools the reporter asked for. 2. Before reaching for script execution, re-fetch the ARIA snapshot with filters; an unclear snapshot often resolves into a usable one and keeps the interaction in the supported click/type toolset (which already covers form filling). 3. When requesting new tools, show the maintainer the exact agent behavior (the reporter's pasted agent quote is what made the case).

Source URL: https://github.com/brightdata/brightdata-mcp/issues/91