Remove a saved request by name (its history entries stay). Returns what was removed.

Remove a variable an agent set (with set_variable). Variables the user defined in the window can only be removed there.

Remove a workflow by name. Returns what was removed.

Turn a saved request (by name) or a history entry (by id) into a curl command, for CI scripts or tools that only speak curl. {{variables}} stay as placeholders, so no secret is written out.

Recent requests from the shared history, newest first: who sent them (gui = the user, cli or mcp = an agent), method, URL, status and time. Credentials are already blanked. Use it to see what the user tried, or to check what was sent earlier.

One history entry in full: when it was sent, the status and time, and the request as sent (credentials blanked, {{placeholders}} kept, so it can be re-sent or saved). The response body is not stored.

One saved request in full: method, URL, headers, body, and the {{variables}} it needs.

Parse a curl command into a Plunger request without sending it: method, URL, headers, body and the {{variables}} it uses. Use it to check what a curl command would do, or with save_as to keep it in the user's Saved list so it can be sent later with send_request by name.

List the requests the user saved in Plunger, by name, with method, URL, headers and the {{variables}} each needs. Call this before building a request from scratch: the user may already have the exact call set up.

List the {{variables}} defined in Plunger. Secret variables are listed by name only (their values are never returned); use them in a request as {{name}} and Plunger fills them in.

List the saved workflows with their steps.

Run a saved workflow: its requests are sent in order, values are carried from one response to the next (never shown if secret), and it stops at the first step that fails. Returns each step's status and the variables it set, plus the last response in full.

Save a request in the user's Saved list without sending it, so it can be re-run by name with send_request (saved_request). Describe it like send_request. {{placeholders}} are kept as written, including in Authorization headers. An existing name is refused unless overwrite is true, which replaces it, so a mistake can be fixed.

Save a workflow: an ordered list of requests where a later one can use values from an earlier response. Each step is described like send_request, plus extract (for example {name: "token", from: "json:$.access_token"}, which keeps the value as {{token}} for the steps after it, hidden if it looks like a credential) and expect_status. Use it for logins, create-then-fetch flows and any sequence you will repeat.

Send an HTTP request through Plunger and get back status, timing, size, headers and the parsed JSON body. Use this instead of curl for API calls: {{variables}} (including the user's secrets, by name) are filled in for you, an undefined {{variable}} makes the request fail safely instead of sending the placeholder, secret values are masked in the result, and the request is recorded in the history the user sees in Plunger. Send a saved request by name with saved_request, or describe one with method, url, headers and a body.

File a saved request or a workflow under a group, such as "Jira" or "Jira/Issues", without touching the request or workflow itself. An empty group takes it out of its group. Use it to tidy the Saved list.

Set a variable that later requests use as {{name}}, for example a token you read from a login response. It persists between calls and runs and is shared with the Plunger window, the CLI and other agents. A secret (or a credential-looking name such as token or api_key) is kept in the system credential store and masked in results. A variable the user defined in the window cannot be changed.