Skip to main content
A finished build keeps the result of the example it ran, so you can check the new tool did the right thing before you rely on it.

​
Read the example result

When the build’s job succeeds, build.example_result holds the example:
  • For a read, the value the tool returned, such as the Google Flights fares it found.
  • For a write, what the build read on the website after making the change, such as Instacart’s order confirmation.
Like any result, the example result is delivered once, so save it when you receive it.
A write build already made its change. Don’t run the new tool with the same input to test it, or you’ll make the change twice.

​
Run the new tool

Pass the job’s tool_id to a run, as in Run a tool. On an integration MCP, list its tools again: the new tool appears under its own name.

​
When the build found an existing tool

build.existing_tool_id names the tool that already covers the task, and tool_id is the same. Nothing new was published; run that tool instead.
  • The new tool joins its website’s integration, build.integration_id. See Use integration MCPs.
  • To remove a tool you built, call DELETE /v1/tools/{id}. It stops running everywhere.