dots.v2.actionGateway.tools.search.get()
Generated on 5 Nov 2026
from DoTs version
v1.23.0
Usage
client.v2.actionGateway.tools.search.get(requestConfiguration?: RequestConfiguration<SearchRequestBuilderGetQueryParameters>): Promise<undefined | Search_tools_response>Description
Returns the tools your team can use that match query, optionally restricted to some providers or to the members of one of your toolbelts. Results are ranked across the whole result set: exact tool name matches first, then name or title prefixes, then name or title substrings, then other matches. Cursor-paged with page_size and page_token; no total is reported.
Parameters
querystring optionalExample:
searchMatched case- and accent-insensitively as a substring of the tool's name, title, description, category, provider ID, or tool slug. Empty matches every tool your team can use.
providerarray of strings optionalExample:
["exa"]Restricts results to these provider IDs, OR'd together. Repeat the parameter to select several. An unknown ID matches nothing.
toolbeltstring optionalExample:
search-toolbeltRestricts results to the members of that toolbelt of your team at its latest version, combined with query and provider as AND. Members are matched at the version the toolbelt pins, which is the same set and the same versions
GET /v2/action-gateway/toolbelts/{name}reports. An unknown or deleted toolbelt returns 404 rather than an empty page.pageSizeinteger optionalExample:
20Page size, 1 to 100. Defaults to 20 when omitted or 0; other values are rejected with 400.
pageTokenstring optionalExample:
ZXhhX3dlYl9zZWFyY2hAMQA
next_page_tokenfrom the preceding response. It is pinned to the query and filters that produced it: replaying one against a different search is rejected with 400, not a silent restart from the top.
Request Sample
Response Example
More Information
See /v2/action-gateway/tools/search in the API reference for additional detail on responses, headers, parameters, and more.