elaichi__synthetic_tool__list
List synthetic tools: multi-step tools defined inside Elaichi — a named input schema over a chain of connector calls — as opposed to the provider tools that come from a connection. Ids are syn_…. Reading and executing are two different gates here, so never infer one from the other. READING: OWNER-SCOPED, and no permission widens it. A synthetic tool carries no ACL — there is nothing to be "shared with me" — so this is exactly the caller’s own tools; toolbox:view and toolbox:manage add nothing, here or on GET /synthetic-tool, so this cannot answer "how many synthetic tools does the organization have" and must not be reported as if it could. A tool missing from this list may therefore mean "not yours" rather than "does not exist" — and synthetic_tool.get answers a tool you may not read with a 404 for the same reason. EXECUTING is no wider: only the tool’s OWNER may run one, because a synthetic tool’s steps run over the owner’s own connections with no re-check at execution. Returns { result: [...], nextCursor, prevCursor } — camelCase here, unlike the REST API’s next_cursor. Unlike the other lists in this catalog limit defaults to 200 rather than 50, so one call is the entire set for almost every organization. It is still a PAGE: a non-null nextCursor means there are more rows, and the only way to reach them is to send it back as cursor until it comes back null. A page whose nextCursor is not null is never a total.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Rows per page, 1–200. Defaults to 200 — the whole set in one call for almost every organization — rather than the 50 the other lists here default to. Larger values are clamped, not rejected. | |
| cursor | No | Opaque cursor taken verbatim from a previous call’s `nextCursor`. Omit for the first page. |