Get Store and Ad Connection Status
get_ecommerce_connection_statusReturns each store and ad account connected to the company with its status, as the doola dashboard shows it. type is 'sales' for stores or 'ads' for ad accounts; omit it for both. Call it before answering from orders, products, sales or ad data. When dataMayBeOutOfDate is true, still answer from the data but say that platform's numbers may be out of date: with reconnectInApp true the user reconnects it on the page at integrationsPageLink, otherwise they contact doola support. When syncInProgress is true its first sync is still running, so never report zero for it. An Unknown status could not be checked right now: answer from the data, say its numbers may be out of date and suggest asking again shortly. A Pending connection was never finished: report no numbers for it and point to integrationsPageLink. An empty connections list means nothing is connected: say so instead of reporting zero and share integrationsPageLink, where stores and ad accounts are connected once doola bookkeeping is set up. Never mention sync dates or why a platform rejected the connection. Answer in plain language and never show the user the field names. It reads the active company; for another company the user owns, pass its companyId from list_companies instead of switching the active company.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "get_ecommerce_connection_status"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | OPTIONAL 'sales' for the store connections behind orders and products, or 'ads' for the ad accounts behind campaigns. Omit to check both. | |
| context | No | Optional, for analytics only. In one sentence, why you are calling this tool and how it serves the user's goal. Describe the purpose in general terms: never include names, emails, phone numbers, addresses, IDs or any other personal details. | |
| companyId | No | OPTIONAL. The doolaCompanyId (an id like '30E5c1AQA326uOuDlsic4No7zZ5'). LEAVE THIS EMPTY/UNSET to use the customer's currently active company — that is the correct default for almost every question. Pass a value ONLY when the customer explicitly references a *different* company they own (e.g. 'show me transactions for my other company X'). NEVER pass a company name, slug, or human label here — only an exact id string. | |
| llm_model | No | Optional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess. | |
| conversation_id | No | Optional, for analytics only. The exact conversation_id from this server's previous response, unchanged. The first response provides one, so leave this out until you have it and never invent one. Keep passing the same value for the rest of the conversation, even when the user moves on to a new request. |