The agent-ready web: Simplify user actions with WebMCP — Tara Agyemang, Google

TL;DR

• 1

  Agents waste huge effort on simple web tasks: Tara shows a ticket-buying example where an agent may inspect the full DOM, accessibility tree, screenshots, and click coordinates just to buy two Afro Beats Festival tickets, only to fail if an ad shifts the page.

• 2

  Good web fundamentals come first: She stresses that semantic HTML, accessibility, fast performance, Core Web Vitals, and clean user flows already make a site much more usable for agents before adding WebMCP.

• 3

  WebMCP gives agents a menu of tools instead of forcing them to guess: Described as the "USB-C of AI agent interactions," the proposed standard lets sites define structured actions that improve reliability and reduce token-heavy browser automation.

• 4

  The live demos show the difference clearly: In the maze game, Gemini 1.5 can call tools like start game, move, look, pick up, drop, and use item, while the concert demo on Gemini 3.1 chains search concerts, open concert page, and purchase ticket to buy two VIP tickets for £356.

• 5

  WebMCP is not the same as MCP: MCP connects agents to server-side applications and can run anywhere, while WebMCP is a browser-specific, client-side implementation of the tools concept and only works with the browser window open.

• 6

  The API is already testable, but very experimental: Early preview works in Chrome 146+ or Chrome Canary with a testing flag, plus Google's Model Context Tool Inspector extension, and Tara warns that the API has been changing week to week.