Delete collection ticket comment in GitLab
Issue Tracking API · write, waits for approval · 10% field coverage
Your agent can delete collection ticket comment in GitLab through Apideck's Issue Tracking API, the same call it makes for every Issue Tracking app. It changes data in the customer's GitLab account, so it stops with the exact request until a person approves it. Apideck adds the customer's GitLab credentials, so no token ever reaches the agent.
The call
DELETE https://unify.apideck.com/issue-tracking/collections/{collection_id}/tickets/{ticket_id}/comments/{id}
Headers: x-apideck-service-id: gitlab, plus your app id and the customer's consumer id. Apideck MCP tool: issue-tracking-collection-ticket-comments-delete. Agent operation id: unified.issue-tracking.collectionTicketCommentsDelete.
| Parameter | In | Description |
|---|---|---|
| id · required | path | ID of the record you are acting upon. |
| collection_id · required | path | The collection ID |
| ticket_id · required | path | ID of the ticket you are acting upon. |
More for collection ticket comments in GitLab
list_collection_ticket_commentscreate_collection_ticket_commentget_collection_ticket_commentupdate_collection_ticket_comment
Delete collection ticket comment 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)Jira