List integrations
list_integrationsLists the marketplace integrations backlane offers (OTTO Market, Kaufland, Mirakl marketplaces, and Mirakl Ads for Sponsored Products advertising on Mirakl retailers), which ones this organization has connected, and for every other one a setup link and what the user needs for it. Call it first when there is no connection for the marketplace or feature the user asks about (e.g. ads on a Mirakl marketplace without a Mirakl Ads connection), when a connection is broken, or when the user wants to connect a marketplace.
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": {
"context": "<context>",
"llm_model": "<llm_model>"
},
"name": "list_integrations"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| context | Yes | Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution." | |
| platform | No | Only this platform. "mirakl" also returns a setup link per Mirakl marketplace; "mirakl_ads" is advertising on Mirakl retailers. | |
| llm_model | Yes | The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess. | |
| conversation_id | No | Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request. |