> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pomerado.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Check the example result

> Read what a finished build's example returned, then run the new tool.

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.

```json theme={null}
{
  "status": "succeeded",
  "tool_id": "tool_9c1d4e7f2a3b4c5d8e6f7a8b9c0d1e2f",
  "build": {
    "integration_id": "int_3b2a1f0e9d8c7b6a5f4e3d2c1b0a9f8e",
    "example_result": {
      "fares": [{ "airline": "Example Air", "price": "$189" }]
    },
    "existing_tool_id": null
  }
}
```

Like any result, the example result is delivered once, so save it when you receive it.

<Note>
  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.
</Note>

## Run the new tool

Pass the job's `tool_id` to a run, as in [Run a tool](/guides/tools/run-tools). 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.

<Accordion title="Details">
  * The new tool joins its website's integration, `build.integration_id`. See [Use integration MCPs](/guides/integration-mcps/overview).
  * To remove a tool you built, call `DELETE /v1/tools/{id}`. It stops running everywhere.
</Accordion>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.