Very poor5.1%

Sites exposing tools in August 2026

What the Sites exposing tools in August 2026 is, and how it is measured

Measured on 14,374 pages, 95.8% of which carried the agentic category, with a confidence margin of ±0.44 pp.

▲ +0.6 pp
Sites exposing tools in August 2026 over 4 months

0.0%5.1%

5.6%0.0%Sites exposing tools · May: 0.0%Sites exposing tools · June: 0.0%Sites exposing tools · July: 4.5%Sites exposing tools · August: 5.1%Sites exposing toolsMayJuneJulyAugust
Sites exposing tools, May 2026 to August 2026, one measurement a month. The last step was a real rise.

What this measures

Who moved

How to read these figures

Every figure here comes from a sample, not from counting every site — so it carries a margin: how much it could move if we had happened to sample different pages. A figure measured on a thousand pages has a wide margin; one measured on a hundred thousand has a narrow one. It matters for one thing: two figures that differ by less than the wider of their margins are not one above the other, they are tied. That is why nothing here has a position number.
SegmentJuly 2026August 2026Movement
core-js 3523675▲ +152
Open Graph568700▲ +132
Apple Pay362492▲ +130
Priority Hints572702▲ +130
HTTP/3575701▲ +126
Cloudflare577702▲ +125
core-js575700▲ +125
HSTS577702▲ +125
Shopify577702▲ +125
Shop Pay330447▲ +117
All sites624735▲ +111
PayPal323403▲ +80
Cart Functionality520595▲ +75
Mastercard285356▲ +71
Visa285356▲ +71

How to move it on your own site

3 · Act

20% of the score

Your site exposes WebMCP tools an agent can actually call.

The other three make your site readable; this one makes it usable. An agent that can call a real search, a real availability check or a real booking does the thing instead of describing it. It is also the rarest: fewer than five in a hundred sites expose anything, which is why it carries the least of the three weights — for now.

What to do

  1. Pick the two or three things people actually come to your site to do. That is your tool list, and a short honest one beats a long speculative one.
  2. Register them with the WebMCP browser API, declaring a schema for the arguments each one takes.
  3. Make sure the schema validates: a tool an agent cannot call correctly is worse than no tool, because it will try.
  4. Describe your forms well enough to be completed: the audit also looks at whether the fields an agent would fill are identifiable.
  5. Treat it as a real interface, with the same care as a public API. Someone will call it without reading anything.

The most work and the least immediate return. Worth doing when the other three are done — or first, if being early matters to you.