Skip to main content
Glama

submit_form

Submit a form using requestSubmit() to trigger framework submit listeners and HTML validation, falling back to legacy methods.

Instructions

Submit a form, honouring framework-level submit listeners.

    Uses ``form.requestSubmit()`` so React/Vue/Formik ``onSubmit``
    handlers fire and HTML validation runs, falling back to a bubbling
    ``submit`` event and finally ``form.submit()`` for ancient pages.
    Returns an error if the selector matches no form.
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorNoform

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden. It explains the fallback strategy, HTML validation, and error handling. It does not cover potential side effects like navigation or page reload after submission, but these are somewhat implied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise with three sentences: purpose, behavior details, and error condition. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the existence of an output schema, the description doesn't need to explain return values. It covers the main behavior and error case, but lacks information about post-submission actions like waiting for navigation. Still, it is reasonable for a simple form submission tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter 'selector' has a default value 'form' but the description does not add meaning beyond the schema. It does not clarify that it is a CSS selector or how it works. Schema description coverage is 0%, so the description should compensate but fails to do so adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool submits a form using requestSubmit() with fallback mechanisms, which is specific and distinguishes it from sibling tools like fill_form or click. The verb 'submit' and resource 'form' are explicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use it (for framework-level submit listeners) but does not explicitly state when not to use it or provide alternative tools. The context of fallback behavior gives implicit guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/bituq/zendriver-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server