List collections in GitLab
Issue Tracking API · read · 74% field coverage
Your agent can list collections in GitLab through Apideck's Issue Tracking API, the same call it makes for every Issue Tracking app. It only reads, so it runs straight away; what GitLab returns is screened before the agent sees it. Apideck adds the customer's GitLab credentials, so no token ever reaches the agent.
The call
GET https://unify.apideck.com/issue-tracking/collections
Headers: x-apideck-service-id: gitlab, plus your app id and the customer's consumer id. Apideck MCP tool: issue-tracking-collections-all. Agent operation id: unified.issue-tracking.collectionsAll.
| Parameter | In | Description |
|---|---|---|
| cursor | query | Cursor to start from. You can find cursors for next/previous pages in the meta.cursors property of the response. |
| limit | query | Number of results to return. Minimum 1, Maximum 200, Default 20 |
| sort[by] | query | The field on which to sort the Collections |
| sort[direction] | query | The direction in which to sort the results |
More for collections in GitLab
List collections in other Issue Tracking apps
The same call works for each of these; only the service id changes.
GitHubGitHub Enterprise Server (on-prem)GitLab server (on-prem)JiraLinearLinear Multiworkspace