elaichi__template__list
List template DEFINITIONS visible to the caller: their own, plus every one explicitly shared with them, with one of their teams, or with the whole organization — and nothing else. No permission widens it. template:view and template:manage add nothing here, and this cannot answer "how many templates does the organization have". Unlike connections and toolboxes, templates carry no org-wide oversight path at all — not here, not in the REST API, not in the Elaichi web app: an org owner/admin sees a template only when they own it or it has been shared with them, whatever permission they hold. A template is a group of tools with frozen/default params; it NEVER references a connection, so it is not itself runnable — stamp a toolbox from one with toolbox.create (template_id). Ids are tpl_…. 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. |