webform_listList all Drupal webforms with optional filters and pagination, helping AI assistants inspect available forms for site operations.
List all webforms.
| Name | Required | Description | Default |
|---|---|---|---|
| filters | No | ||
| page_limit | No | ||
| page_offset | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It does not disclose read-only safety, authentication needs, pagination behavior, or how the optional filters affect results, leaving significant gaps for a list operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is very short and front-loads the core action, but it is under-specified rather than appropriately concise. A single six-word sentence does not provide enough structure for an agent to understand scope or usage.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return values need not be explained, but the description still omits usage guidance and any parameter meaning. For a three-parameter list tool with no annotations and 0% schema description coverage, it is too incomplete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description adds no meaning for any of the three parameters. The word 'all' may even mislead, since the schema provides filters and pagination parameters that are entirely unexplained.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb and resource: 'List all webforms.' That is specific enough for an agent to recognize the tool's basic purpose, but it does not distinguish this from siblings such as webform_get or webform_submission_list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives like webform_get for a single form or webform_submission_list for submissions. The implied usage is simply listing forms, with no exclusions or selection criteria provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.