Agentic Web CensusCheck your site
EN

Trends · Sites exposing tools

Sites exposing tools across the web

Sites exposing WebMCP tools an agent can call. It has gone up since May 2026, and again last month. Both steps clear their margin.

Very poor4.6%

Sites exposing tools in September 2026

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

Measured on 158,176 pages, 95.3% of which carried the agentic category, with a confidence margin of ±0.13 pp.

▲ +0.2 pp
Sites exposing tools in September 2026 over 5 months

0.0%4.6%

5.1%0.0%Sites exposing tools · May: 0.0%Sites exposing tools · June: 0.0%Sites exposing tools · July: 4.6%Sites exposing tools · August: 4.4%Sites exposing tools · September: 4.6%Sites exposing toolsMayJuneJulyAugustSeptember
Sites exposing tools, May 2026 to September 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.
SegmentAugust 2026September 2026Movement
HTTP/36,2416,931▲ +690
Apple Pay3,9154,598▲ +683
Priority Hints6,2376,914▲ +677
Cloudflare6,2726,943▲ +671
HSTS6,2736,944▲ +671
core-js6,2676,934▲ +667
Shopify6,2766,941▲ +665
Open Graph6,2336,895▲ +662
Shop Pay3,5644,211▲ +647
core-js 36,0476,685▲ +638
All sites6,6057,237▲ +632
Cart Functionality5,5816,122▲ +541
PayPal3,4063,892▲ +486
.com3,8884,281▲ +393
Google Analytics4,4524,837▲ +385

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. Declare them on the forms you already have: two attributes on the form, one per field, and the browser builds the tool. Reach for the scripted API only for a tool that is not a form.
  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.
<form method="get" action="/search"
      toolname="search_products"
      tooldescription="Search the catalogue and return matching products with their prices.">
  <label for="q">What are you looking for?</label>
  <input id="q" name="q" type="search"
         toolparamdescription="Words describing the product, such as: 12 mm bevel-edge chisel">
  <button type="submit">Search</button>
</form>
htmlWebMCP declared on a form you already have: the browser reads the fields and builds the tool. No script, and no `toolautosubmit` — a person confirms before an agent spends 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.