tool:read, granted by the platform API key scope tools.read.
Path parameters
Query parameters
Tool types
Thetype values are http, mcp, searchai, workflow, table, integration, and connector. The list includes only the types that are enabled for public API execution. The table type is enabled by default. The other types are opt-in for each environment.
The connector type is the older stored name of integration. The list can return either value, so treat them as the same type.
Authentication
Use one of the supported credentials:x-api-key: abl_...for a platform API key.Authorization: Bearer <abl_... | JWT>for a platform API key or Studio user JWT.auth: <assertion>for a JWT App assertion.
pk_...) are not accepted. The JWT App assertion must be sent in the auth header, not the Authorization header.
Response
A successful response containssuccess and data. The data object includes:
Each tool summary can include
name, type, description, effect, requiresAuthProfile, operations, executable, and unsupportedReason, depending on the tool.
The executable property indicates whether a tool can be invoked through this API. The unsupportedReason property, when present, explains why it cannot be executed.
To retrieve the input schema for a tool, use Describe a tool and its input schema.
Errors
The
429 response uses a rate-limiter-specific response format rather than the standard API error envelope. Check the response headers for rate-limit information and retry guidance.