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

# List the available project tools

Lists the tools available for execution in a project. Each result provides a tool summary, including its name, type, description, declared effect, and execution availability. The endpoint returns only tools whose types are enabled for public API execution.

Use this endpoint to discover available tools before retrieving a tool's input schema or invoking it. Results are paginated using a cursor based on the tool name.

**Permission:** `tool:read`, granted by the platform API key scope `tools.read`.

## Path parameters

| Parameter | Type | Required | Description |
| - | - | - | - |
| `projectSlug` | string | Yes | Project slug, not the project ID or UUID. |

## Query parameters

| Parameter | Type | Required | Description |
| - | - | - | - |
| `limit` | integer | No | Number of tools to return per page. Defaults to `50`, with a minimum of `1` and a maximum of `200`. The value is clamped to the configured maximum. |
| `cursor` | string | No | Opaque cursor returned in `nextCursor` by the previous response. Omit it to retrieve the first page. |
| `type` | array of strings | No | Restricts results to specified tool types. Repeat the parameter to specify multiple types. |

Supported tool types include `http`, `mcp`, `searchai`, `workflow`, `table`, `integration`, and `connector`. The legacy persisted value `connector` represents `integration`. Types that this API surface never serves are rejected rather than silently returning an empty page.

## Authentication

Use one of the supported credentials:

* `x-api-key: abl_...` — platform API key.
* `Authorization: Bearer <abl_... | JWT>` — platform API key or Studio user JWT.
* `auth: <assertion>` — JWT App assertion.

Public SDK keys (`pk_...`) are not accepted. The JWT App assertion must be sent in the `auth` header, not the `Authorization` header.

## Response

A successful response contains `success` and `data`. The `data` object includes:

| Property | Description |
| - | - |
| `environment` | Environment against which tool definitions were resolved. Always `draft` on this API surface. |
| `tools` | Array of tool summaries. |
| `nextCursor` | Cursor for the next page, or `null` when no more results are available. |

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 the **Describe a tool** endpoint.

## Errors

| HTTP status | Description |
| - | - |
| `400` | Invalid request, including an invalid tool type filter. |
| `401` | Missing or invalid credentials, or an unsupported public SDK key. |
| `403` | The credential lacks the required permission or project access. |
| `404` | Project or resource not found. |
| `429` | Tenant request or tool-call rate limit exceeded. |

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.


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