# Url Params To Json — REST API endpoint `url-params-to-json`

Parse URL query parameters into a JSON object. Accepts a full URL or a bare query string, decodes values, strips a trailing "[]" from keys, and collapses repeated keys into arrays.

- Category: data
- MCP server: https://mcp.findutils.com/ (Streamable HTTP, no API keys, 120 req/min per IP)
- REST endpoint: POST https://api.findutils.com/api/tools/url-params-to-json/execute (no API keys, 60 req/min per IP)
- Reference page: https://findutils.com/api/url-params-to-json/
- Same tool on the other surface: https://findutils.com/mcp/url-params-to-json/

## Call the endpoint (verified example)

```bash
curl -X POST https://api.findutils.com/api/tools/url-params-to-json/execute \
  -H "Content-Type: application/json" \
  -d '{
    "input": "https://example.com/search?q=hello&tags=a&tags=b"
  }'

# Parameter schema
curl https://api.findutils.com/api/tools/url-params-to-json
```

## Input schema

| Argument | Type | Required | Description |
|---|---|---|---|
| `input` | string | yes | A full URL (https://x.com/a?q=1&tags=a&tags=b) or a query string ("q=1&tags[]=a&tags[]=b"). |

Example arguments (verified):

```json
{
  "input": "https://example.com/search?q=hello&tags=a&tags=b"
}
```

OpenAPI 3.1 spec: https://findutils.com/api/openapi.json · Interactive docs: https://findutils.com/api/docs/

## Also an MCP tool

```bash
claude mcp add findutils --transport http https://mcp.findutils.com/
```

Then ask the client to call `findutils:url_params_to_json`. Full MCP reference: https://findutils.com/mcp/url-params-to-json/

---
Full catalog: GET https://api.findutils.com/api/tools · https://findutils.com/api/ · https://findutils.com/llms.txt