Lists AI Tools with optional filtering, search, and pagination.
Returns a paginated list of tools registered under the integration that match the optional type and search filters, with pricing metadata attached. Use `search` for case-insensitive substring matching against tool ID, display name, and description. Use `pageSize`/`pageToken` to page through results. Use `ids` to resolve a known set of tools in a single request — the batch-get case, for callers holding tool references (an agent's attached tools, say) that need their metadata without pulling the integration's entire collection.
Authorization
Bearer JWT Authorization header using the Bearer scheme. Enter 'Bearer' [space] and then your token.
In: header
Path Parameters
The integration identifier
length <= 150The tenant identifier
Query Parameters
Filter by tool types
Restrict to these tool ids. Empty means no id filter.
Lets a caller resolve a known set of tools in one request instead of listing an integration's entire tool collection and filtering client-side. A tool id is unique only within its integration, so this is meant to be combined with a concrete Fruxon.Model.Tools.ToolListRequest.IntegrationId; paired with the wildcard it matches the id across every integration declaring it.
items <= 100int32int32Opaque cursor token from an external system (e.g. RAG API). When set, M:Fruxon.Common.Collections.PageToken.AsString returns this value directly instead of encoding Fruxon.Common.Collections.PageToken.Skip.
Response Body
curl -X GET "https://api.fruxon.com/v1/tenants/string/integrations/string/tools"{
"items": [
{
"id": "string",
"integrationId": "string",
"displayName": "string",
"description": "string",
"toolType": "API",
"actionType": "READ_ONLY",
"resultType": "STRING",
"isAsync": false,
"parametersMetadata": [],
"descriptor": {
"apiTool": null,
"predefinedTool": null,
"mcpTool": null,
"codeTool": null
},
"createdAt": 0,
"modifiedAt": 0,
"pricing": []
}
],
"nextPageToken": "string",
"totalCount": 0
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}{
"type": "string",
"title": "string",
"status": 0,
"detail": "string",
"instance": "string",
"property1": null,
"property2": null
}Imports tools from a remote MCP server into an integration.
The integration is created automatically if it does not yet exist. Tools that already exist within the integration are skipped unless `overrideExisting` is set.
Retrieves a specific AI Tool by ID.
Returns the tool definition (input schema, description, type) along with the pricing metadata used to estimate cost per invocation. The `(integration, tool)` pair is the composite key; the same `tool` ID under a different integration is a different resource.