Most websites still treat forms as conversion components. Name, email, phone, message, button, confirmation. As long as the visitor is human, that simplicity can work. Humans compensate for imprecision, understand context and infer intent.
With AI agents, that tolerance decreases. An agent that helps a user fill a form or choose an action must understand what the site truly exposes. It should not only see a field. It must know what that field represents, why it is required, what action will be triggered and what consequence will follow.
The form becomes an action object
In the agentic web, a form is no longer just a contact point. It becomes a surface where intent can produce action.
That action must be named. It must be bounded. It must be connected to a confirmation. It must also be distinguished from adjacent actions. A general contact form, diagnostic request, quote request and booking should not be exposed as if they were interchangeable.
Common weaknesses
The most common weaknesses are often ordinary:
- placeholders used instead of labels;
- missing or generic
nameattributes; - “Submit” buttons without clear intent;
- errors not associated with fields;
- confirmations that do not say what happens next;
- the same form used for several intents;
- hidden or modified fields after hydration;
- modals or menus that change context without announcing it.
For humans, these are irritants. For an agent, they are ambiguity zones.
WebMCP does not replace the basics
WebMCP becomes interesting when the action is already clear. Adding a structured declaration to a confused action does not solve the problem. It can even expose a bad action more cleanly.
The right sequence is therefore:
- clarify the role of the form;
- fix labels, names, states and errors;
- make the CTA more specific;
- explain the confirmation and consequence;
- evaluate whether the action deserves WebMCP exposure.
The real issue: action legitimacy
An agent may be capable of submitting a form. That does not mean it should do it. Technical capability, user intent and action legitimacy must be separated.
A mature journey should therefore expose cases where the agent can move forward, where it must request confirmation, where it must clarify intent and where it must abstain.
How Pagup intervenes
The WebMCP and agent-friendly forms audit verifies this concrete layer: fields, CTAs, errors, confirmations, states, accessibility tree and WebMCP potential. The Agentic Readiness Audit then broadens the analysis across full journeys.
The goal is not to add a fashionable technology. The goal is to make action readable, stable and defensible.