Skip to main content
Glama

List integrations

list_integrations
Read-onlyIdempotent

Lists 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

NameRequiredDescriptionDefault
contextYesExplain 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."
platformNoOnly this platform. "mirakl" also returns a setup link per Mirakl marketplace; "mirakl_ads" is advertising on Mirakl retailers.
llm_modelYesThe 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_idNoPass 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered; the description adds that unconnected integrations come back with a setup link and prerequisites, which is useful extra context. It does not discuss result size, ordering, or pagination, which is the minor remaining gap.

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

Conciseness3/5

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

The verb and resource are front-loaded, which is good, but the second sentence is a single sprawling clause packing three use conditions, and the first sentence's parenthetical platform glossary duplicates the enum. It is informative but could be split and trimmed without losing routing value.

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 return-value burden and does so: it explains that connected integrations are identified and unconnected ones include a setup link and requirements. Combined with annotations and a fully documented parameter schema, an agent has everything needed to call it correctly.

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 coverage is 100%, so all four parameters are already documented, and the description's parenthetical enumeration of OTTO Market, Kaufland, Mirakl marketplaces, and Mirakl Ads largely restates the platform enum descriptions. With the schema doing the heavy lifting, the description only marginally enriches parameter meaning (e.g. signaling that Mirakl results include a setup link per marketplace).

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?

The description opens with a specific verb and resource ("Lists the marketplace integrations backlane offers") and enumerates the returned contents: which integrations exist, which are connected, and setup links plus prerequisites for the rest. An agent can tell this apart from siblings like request_integration or respond_to_invitation without opening a schema.

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?

It gives an explicit routing rule — "Call it first" — plus three concrete triggering conditions: no connection for the requested marketplace/feature, a broken connection, or a user wanting to connect a marketplace. It even names a specific case (ads on a Mirakl marketplace without a Mirakl Ads connection), leaving nothing to inference.

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.