Skip to main content
Glama

Get Store and Ad Connection Status

get_ecommerce_connection_status
Read-only

Returns 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

NameRequiredDescriptionDefault
typeNoOPTIONAL 'sales' for the store connections behind orders and products, or 'ads' for the ad accounts behind campaigns. Omit to check both.
contextNoOptional, 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.
companyIdNoOPTIONAL. 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_modelNoOptional, for analytics only. Your exact model identifier from your system prompt (e.g. "claude-opus-4-8"), or "unknown" if unsure. Never guess.
conversation_idNoOptional, 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already establish a safe read-only operation, and the description adds extensive behavioral context: status meanings, data freshness handling, reconnect flows, sync state, empty-list handling, and privacy constraints. This goes well beyond what the annotations provide.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded, followed by tightly packed but actionable handling rules. It is longer than average, but almost every sentence provides behavior needed to answer correctly and avoid misleading numbers.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the full burden of explaining what the statuses mean and how to respond. It covers freshness, reconnect, sync, unknown, pending, empty results, active-company behavior, and user-facing language requirements.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, and the schema already documents type, companyId, and analytics parameters in detail. The description reinforces type and companyId usage but adds no significant parameter syntax or constraints beyond the schema, so baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: it returns each connected store and ad account with status, as shown in the dashboard. It also distinguishes this status check from data retrieval by saying to call it before answering from orders, products, sales, or ad data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to call it before data-based answers, explains how to use the type filter, and gives an alternative for another owned company via list_companies. The guidance is specific enough that an agent can choose this tool and configure it correctly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.