Tools
Test Tool
Execute a tool live against the upstream API and return the response, timing, and outbound request details.
POST
Runs the tool through the same execution pipeline that MCP clients hit, but with the admin “Test Tool” affordances: by default it uses the test credentials stored on the tool/server, surfaces the outbound HTTP request for inspection, and records
last_tested_at / last_test_response_ms on success.
This is the endpoint that the Test button in the admin UI calls. Use it to validate a tool’s parameter mapping, headers, and response handling without going through an MCP client.
Draft and inactive tools cannot be tested — publish/activate them first or you’ll get a
422. Pass use_test_credentials: false to execute against production credentials instead of test credentials.Path Parameters
The UUID of the server the tool belongs to (e.g.
836995ae-1cff-41ec-823e-a4f07ccca3a0). Numeric IDs are also accepted for backwards compatibility.The UUID of the tool to test (e.g.
5376af81-6bb8-4b01-800c-508d7672e394). Numeric IDs are also accepted for backwards compatibility.Body Parameters
Object of input arguments to pass to the tool. Keys must match the tool’s
input_schema.properties. Defaults to {}.When
true (default), execute with test credentials so production keys aren’t put through experimentation. When false, execute against live production credentials — the same path an MCP client takes.Response Fields
The exact HTTP request that was dispatched to the upstream API —
method, url, headers, body. Useful for verifying that parameter mapping and templating produced the URL/body you expected. null when the executor short-circuited before issuing a request.The unprocessed upstream response —
status_code, headers, body (always a string). null on transport errors.The MCP-shaped result that an MCP client would have received:
{ content: [{ type, text }], isError }. isError is true when the upstream returned a non-2xx status or the executor itself threw.{ total_ms: <int> } — wall-clock duration of the full test, including auth resolution and response mapping.Status Codes
| Code | Meaning |
|---|---|
200 | Test ran. Check mcp_output.isError to distinguish upstream failure from success. |
404 | Tool (or its parent server) not found. |
422 | Tool status is draft or inactive — not testable in its current state. |

