corestack_ ticket_ subscriber_ remove
Remove a follower from a support ticket.
When to use it
Remove a follower from a support ticket, so they are no longer told of its replies, as the ticket page's Remove button
does. Any follower can be removed, yourself included. Removing someone who does not follow changes nothing. There is
no confirmation: a removed follower can be added back with corestack_ticket_subscriber_add.
Ask for it
Using the Corefinity MCP server, call corestack_ticket_subscriber_remove with ticket_id 48210, user_id 5123. (Remove a follower from a support ticket.) Tell me what it returned.Inputs
client_company_idinteger
The client company the ticket is in, when your agency raised it for a client; your own company when left out. At least 1.
ticket_idintegerRequired
The ticket's number, from corestack_tickets_list. At least 1.
user_idintegerRequired
The follower to remove, an id from corestack_ticket_subscribers_list. At least 1.
The answer is the ticket's followers, as corestack_ticket_subscribers_list answers them (without candidates).
Example call
{
"name": "corestack_ticket_subscriber_remove",
"arguments": {
"ticket_id": 48210,
"user_id": 5123
}
}If it is refused
| Reason | What to do |
|---|---|
tenant_mismatch | There is no such ticket, or it is not in your company (or in client_company_id), or the person only follows it as a subscriber of another company. |
forbidden | You may not change who follows this ticket. |
pin_refused | The token is limited to some sites; a ticket belongs to the whole company. |
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |
The same task elsewhere
Was this helpful?