You can include the ? and the host
A full URL is fine — the tool ignores the path and reads the query. Bare params without ? work too.
JSON Tools for AI Developers · Runs locally
Natural language generation · Schema · Zod · OpenAPI · Function Calling · MCP · 30+ tools
GET query strings get long and hard to read. JSON makes arrays and nested keys obvious.
You can also go the other way: build name=Alice&tags[]=json from an object and drop it into a browser or curl.
Encoding follows common application/x-www-form-urlencoded habits. Recheck docs for framework-specific [] styles.
Query strings that contain tokens are converted locally.
A full URL is fine — the tool ignores the path and reads the query. Bare params without ? work too.
tags[]=a&tags[]=b and tags=a&tags=b are both common. Check whether you got an array or last-write-wins, then match your backend.
Common tags[]=a&tags[]=b becomes an array. Plain repeated keys may become an array or last-write-wins, depending on the implementation.
Either works. You can paste params only. Host and path are ignored.
It uses URL encode/decode. If the source is already wrongly encoded, fix the source first.
No.
GET is a URL query string. Properties is a Java-style key=value file.
An x-www-form-urlencoded body can be pasted as params. A JSON body belongs on the Format page.
In form encoding, + is often a space. Confirm the source if + appears in a path.
Keys like flag= are kept; the value may be an empty string. Adjust if your backend treats "missing" differently.