Run folder
run_folderRuns every saved request in a folder or workspace in order, with scripts and assertions, to verify an API still works after a change. Filter by tags, repeat with data, and get counts plus failed checks.
Instructions
Send every request in a folder, or in the whole workspace, in order, with scripts and assertions, the way the collection runner does. tags and exclude_tags narrow the run to a subset such as smoke tests; data and iterations repeat it. Use it to check that an API still works after a change. Returns the counts and, for failed requests only, the error, the failed checks (failedTests) and the console output.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "run_folder"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| bail | No | Stop at the first failing request. | |
| data | No | Run once per item; each item's fields become variables for that iteration, such as [{"userId": 1}, {"userId": 2}], and win over the environment and a request's own vars. | |
| tags | No | Run only requests with at least one of these tags, as list_requests shows them. Case does not matter. | |
| folder | No | The folder to run, by name or path. Leave out to run every request in the workspace. | |
| iterations | No | Repeat the run this many times, or use only the first rows of data. | |
| exclude_tags | No | Skip requests with any of these tags. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hint | No | ||
| summary | No | ||
| failures | No | ||
| withheld | No | ||
| durationMs | No | ||
| iterations | No | ||
| unresolved | No | ||
| environment | No |