Domain Redirects
domain-redirectsUse when the user asks where a domain redirects, whether domains are aliases, or to detect brand consolidations. Single-domain lookup.
Returns known redirects from or to the given domain.
Input parameters (filters): domain, match. Definitions in input schema.
Available output fields for the 'fields' parameter: source_domain, source_fqdn, linked_domain, linked_fqdn, record_date. Field details: https://docs.discolike.com.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"filters": "<filters>"
},
"name": "domain-redirects"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fields | No | Output fields to include in response | |
| format | No | Response format: rows or columnar | rows |
| context | No | Why you are calling this tool, in a few words. No names or emails. | |
| filters | Yes | Request filters for domain redirect lookup. | |
| llm_model | No | Your model id, or "unknown". | |
| conversation_id | No | The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | ||
| redirects | No | ||
| _mcp_instructions | No | Server-issued metadata for this conversation. |