Skip to content

List connector tools (catalog capability)

GET /connector/{slug}/tools

Every tool this connector defines, each flagged `restricted`/`restricted_by` for the caller — the catalog view, with no account behind it. Use it to pick `tool_name` values for toolbox entries. For what one authenticated account can actually run, use `GET /connection/{id}/tools`. Blocked tools are flagged, not omitted; the model-facing `connector.list_tools` operation still omits them, because a tool a model may not call is a wasted turn while a person picking one needs to see why it is unavailable. A restricted connector answers 403. Requires `connector:view`.

Path Parameters

slugstring
required·

Connector slug.

Response Body

next_cursorstring,null
prev_cursorstring,null
resultobject[]
descriptionstring
input_schemaRecord<string, any>

JSON Schema for the tool arguments.

methodstring
namestring

Exact tool name — what a toolbox entry's tool_name must contain.

resourcestring
restrictedboolean

True when the caller's restrictions block THIS tool. Blocked tools are returned flagged, never omitted — a shorter list is no signal, because nobody knows the length it should have been. Presence is not permission: execution still refuses it. The connector-level 403 is a separate question and is unchanged.

restricted_bystring,null

Which precedence layer's rule blocks this tool, null when none does. Same field, union and meaning as on connector and connection rows: adds which to restricted's whether and nothing else — no rule id, author, reason or coverage. restricted === (restricted_by !== null) always.

Possible values:
roleusernull
restricted_scopestring,null

"connector" when the tool is refused because its WHOLE connector is restricted for the caller, "tool" for a rule about the tool itself, null exactly when restricted_by is. Decides which ask can succeed: a tool request on a connector restricted whole is refused (409 tool_request_connector_blocked), so ask for the connector. On this listing it is only ever "tool" when set, since a connector restricted whole 403s the route; toolbox entries carry the same field and can say "connector".

Possible values:
connectortoolnull 
curl -X GET 'https://api.elaichi.ai/connector/<slug>/tools' \
  -H 'Authorization: Bearer $ELAICHI_API_TOKEN' \
  -H 'Content-Type: application/json'
const response = await fetch('https://api.elaichi.ai/connector/<slug>/tools', {
  method: 'GET',
  headers: {
    'Authorization': 'Bearer ' + process.env.ELAICHI_API_TOKEN,
    'Content-Type': 'application/json',
  },
});

const data = await response.json();
console.log(data);
import os
import requests

url = "https://api.elaichi.ai/connector/<slug>/tools"
headers = {
    "Authorization": f"Bearer {os.environ['ELAICHI_API_TOKEN']}",
    "Content-Type": "application/json",
}

response = requests.get(url, headers=headers)
print(response.json())