corestack_ redirects_ get
Redirects.
When to use it
A row's redirect rules in position order, with their ids and the table's version — which corestack_redirects_update needs. An exact match, including a prefix rule's own path, is taken first whatever its position; prefix and regex rules are then tried in order. Rules limited to a domain run before the every-domain rules.
Ask for it
Using the Corefinity MCP server, call corestack_redirects_get with site_id 4211. (Redirects.) Tell me what it returned.Inputs
site_idintegerRequired
At least 1.
Example call
{
"name": "corestack_redirects_get",
"arguments": {
"site_id": 4211
}
}If it is refused
| Reason | What to do |
|---|---|
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. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
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?