Logs for a tool records every time an AI agent, an MCP server, or a REST API caller invoked it, with the status, duration, and a trace view of each step's input and output. Use it to confirm a tool is being called as you expect, find a specific record's run by its trace key, and see exactly what a step sent and received when a run failed. This article is for integrator.io users and administrators who monitor tools. Tools called from flows and APIs are logged with the flow or API instead.
Before you begin
- Execution logging is turned on for the account. See Introduction to execution logs.
- The invoking agent or MCP server has a log level other than No logging. The tool inherits the caller's log level; you can't set it per tool.
- For a non-production environment, your account has a multi-environment license.
Test runs appear only in the Run console, not here — see Test a tool in Tool builder. Invocations from flows appear in flow run logs, and invocations from APIs in API request and execution logs.
Open the logs
- Go to AI studio
, and then select Tools.
- Select the tool, and then select Logs.
Search and filter
- Search filters the list by text.
- The date range (default Last 5 mins) offers presets and Custom range, where you set Start time, End time, and Timezone, and then Apply. Clear removes it.
- The Resource type, Resource name, and Status columns have filters.
- Select Refresh
to reload the list.
Invocation list
| Column | Description |
|---|---|
| Time | When the invocation started. |
| Resource type | AI Agent, MCP Server, or Standalone (a direct REST API call). |
| Resource name | The agent or MCP server; for a REST API caller, the caller's IP address. |
| Status | Whether the run succeeded or failed. |
| Duration (ms) | Elapsed time in milliseconds. |
| Trace key | The value of the tool's trace key template for this record, if one is set. See Configure tool input. |
| Triggered by | The account owner for agent invocations; the token's owner for MCP and REST API invocations. |
| Open trace view | Opens the trace view. A Debug badge marks invocations logged at the Debug level. |
Trace view
The trace view shows the run step by step. The left pane lists the steps in order, from the Tool input boundary through each step to the Tool output boundary; nested tools appear inline, up to five levels deep. Select a step to see its input and output in the right pane.
- Where request and response detail is available, Request shows General details, Headers, and Body, and Response shows what the application returned. Select Copy to copy a payload.
- A step that processed several records shows a child list you can filter by status and page through.
Request and response detail is available for HTTP, NetSuite, and Salesforce connectors. Other connectors show the step's input and output only.
Salesforce steps log request and response detail at lower levels than other connectors. At Basic, successful steps record metadata only, and failed steps also record the request and response. Standard records the request and response for every call, and Detailed records them as flows do. Debug adds the inputs and outputs of mappings, transformations, and similar step components.
Log levels
The log level is set on the invoking agent or MCP server and applies to every tool it calls.
| Level | What's recorded |
|---|---|
| No logging | No invocation details are stored. Logs stays empty for this caller. |
| Basic | The invocation, its status, and its duration. |
| Detailed | Basic, plus each step's input and output. |
| Debug | Detailed, plus request and response detail, for the duration you set on the agent or MCP server (for an MCP server, 5 minutes up to a plan-based maximum: 15 minutes on a free trial, 1 hour on Standard, 24 hours on Professional, 72 hours on Enterprise). |
Delete logs
Account owners, administrators, and users with Manage access can delete a tool's logs.
- On Logs, select Delete logs.
- Choose the date range.
- Select Delete logs.
Limitations
- Test runs aren't logged here.
- Invocations that happened before execution logging was enabled aren't available.
- Logs for a deleted tool aren't available.
- Salesforce file operations (ContentVersion, Attachment, and Document) and connection activity outside a tool run aren't logged.