input_schema.json is the “face” of a script. By modifying this file, you can control what parameters users need to fill in before running the script (such as URLs, keywords, dates, etc.), and how these inputs are presented (dropdowns, checkboxes, text fields, and more).
1. Overall Structure
A standard configuration file consists of the following three parts:- description: Introduces the purpose and usage of the script to users.
- b (Concurrency Key Field): Determines how the script splits tasks.
- properties: The list of configurable parameters.
💡 Example

2. Root Field Descriptions
| Field Name | Required | Description |
|---|---|---|
| description | No | Tool description. Displayed at the top of the page. Used to explain the script’s purpose, usage notes, and limitations. |
| b | Yes | Task split key. Must match the name of one property. The script will run concurrently based on this field (e.g., split tasks by number of URLs). |
| properties | Yes | Parameter configuration list. Each element represents an input field or selector on the UI. |
3. Parameter Properties (Inside properties)
Each parameter item can include the following attributes:
- title: Label shown on the UI (e.g., “Search Keywords”).
- name: Internal identifier, must be unique and must not contain Chinese characters.
- type: Data type:
string: Textinteger: Numberboolean: Boolean (true / false)array: List / multiple valuesobject: Object
- editor: Determines how the input is rendered in the UI (see below).
- description: Helper text shown below the input field.
- default: Default value shown initially.
- required: If set to
true, the script cannot run unless this field is filled.
4. Editor Type Guide
Choose different editors to optimize user experience.4.1 Basic Text & Numbers
| Editor | UI Display | Use Case |
|---|---|---|
| input | Single-line text field | Short text, keywords, usernames, etc. |
| textarea | Multi-line text field | Long-form text input. |
| number | Numeric input | Only allows numeric values with range control. |
4.2 Selectors
| Editor | UI Display | Description |
|---|---|---|
| select | Dropdown | Ideal for many predefined options. |
| radio | Radio buttons | Single selection from multiple options. |
| checkbox | Checkboxes | Multiple selections allowed. |
| switch | Toggle switch | Used for on/off states. |
4.3 Date & Special Lists
| Editor | UI Display | Description |
|---|---|---|
| datepicker | Date picker | Select or input dates. |
| requestList | URL list | Batch input and management of target URLs. |
| requestListSource | URL list with parameters | Extends requestList with custom parameters. |
| stringList | String list | Batch input for keywords or similar data. |
5. Common Component Examples
5.1 Single-line Input

5.2 Multi-line Textarea

5.3 Number Input

5.4 Dropdown Select

5.5 Radio Buttons

5.6 Checkboxes

5.7 Date Picker



5.8 Switch

5.9 URL List (requestList)

5.10 URL List Source (requestListSource)

5.11 String List

💡 Configuration Tips
-
Write clear descriptions
A well-written
descriptionimproves discoverability and usability. - Provide sensible defaults Good defaults allow users to run the script with minimal effort.
-
Enforce required fields
For critical parameters (e.g., login cookies or start URLs), always set
"required": true.