Retrieves traffic source templates, optionally filtered and paged.

Filter and page server-side rather than fetching the whole collection and filtering locally.

Filters combine with AND, and each filter parameter's own description states whether it matches exactly or as a case-insensitive substring. Filters are applied before paging, so a page contains only entities matching the filters.

Send limit to page; without it this endpoint returns the whole matching collection - but the MCP list_ tools default limit to 100, so through them a bare call is one page, not the complete collection.

Paging is by cursor, not by position: a response that has more to give carries nextId, and you get the following page by sending it back as the nextId parameter with the same filters. When nextId is absent the collection is exhausted - there is no need for a further request to discover that, and no total count to compare against. Do not construct a cursor yourself; ids are opaque here.

Freshness (If-Modified-Since) is judged over every entity of this type, not over the filtered page: a change that moves an entity out of your filter, or onto a page you are not reading, still answers 200. So the header combines with both filtering and paging, at the cost of the occasional 200 for a view that did not itself change.