b2KIT

Redis Command Builder

Build Redis commands visually with data structure selection, arguments, and command documentation.

Tested tool guide Tested browser tools Checked August 16, 2026

What Redis Command Builder does, with a checked example

Choose a data structure - String, Hash, List, Set, Sorted Set, or Stream - and the command catalog narrows to the operations that can act on that structure. Pick a command, fill the argument slots it presents (key, value, options), and the tool assembles the finished command line while showing that command's documentation beside it. The surprise most users hit is that this is a syntax builder, not a client: it never connects to a Redis server, and the line it produces becomes real only when you paste it into redis-cli or run it through a client library.

Worked example

A concrete input and expected output from the current implementation.

Input

Structure: String / Command: SET / Key: greeting / Value: hello / Option: EX 60 seconds

Expected output

SET greeting hello EX 60

SET stores the value at the key, and EX 60 appends a 60-second time-to-live, so the key expires exactly one minute after the command runs. The builder places options after the key and value, in the order the SET signature documents, so the result reads the way redis-cli expects it.

How the result is produced

1

Structure-driven command filter

Selecting a data structure narrows the palette to the commands registered for it, and the chosen command drives the argument panel, which shows exactly the inputs its signature defines, with options as toggles or fields. The filter blocks pairings the server would reject, such as LPUSH on a String key, which fails with a WRONGTYPE error.

2

Assembly in signature order

Arguments are joined in the order the command reference documents them, one space apart, with options appended after key and value. The completed line renders in a copy field - a single click copies it ready for redis-cli - and the command's documentation excerpt appears alongside, so you can read what each option does before copying. Nothing is executed or validated against a live server.

Good uses

  • Learning Redis: see which options a command accepts, such as SET's NX, XX, and EX, with its documentation in view.
  • Assembling a fiddly command without misremembering syntax, like ZADD with several score-member pairs or a SET that combines an expiry with NX, then copying the result into redis-cli.
  • Checking argument order for a rarely used operation, such as sorted-set or stream commands where the score-before-member convention is easy to get backwards.

Limits and checks

  • The tool cannot see your server's Redis version. A command that assembles cleanly may use an option your installed Redis does not support, such as one introduced in a newer release, so a buildable line is not a guarantee that it will run on your server.
  • Values containing spaces, quotes, or shell metacharacters are not escaped. Pasted into a terminal they need manual quoting, or the shell will split the command differently than you intended.
  • Valid syntax is not the same as correct intent: SET without NX silently overwrites an existing key, and swapping score and member in ZADD parses fine while storing the opposite of what you meant. Review the assembled line before running it against real data.

Common questions

Does this tool execute the command against my Redis server?

No. It only assembles command text for you to copy into redis-cli or a client library. Everything runs in the browser, nothing connects to a server, and the tool itself never creates or modifies a key. You remain responsible for quoting, picking the right database, and checking the reply.

What is the difference between the NX and XX options on SET?

NX makes the write succeed only when the key does not yet exist; XX makes it succeed only when the key already exists. Use NX to create-if-missing and XX to update-if-present. With neither option, SET simply overwrites whatever is stored. The server replies OK on success and nil when the condition is not met.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools