Skip to main content
Glama

List my integrations

list_integrations
Read-onlyIdempotent

Integrations: Use when a signed in customer asks about their own integrations or a setup they planned: each with its id, systems, status, record types, last sync, failed and waiting records and a next step, plus their planned concepts. Not for what CRM Connector offers (use get_integration_options) or why records failed (use get_integration_health).

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": "list_integrations"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
outcomeYes
summaryYes
conceptsNo
setUpUrlNo
integrationsYes
availableSystemsNo
moreInformationUrlYes
failedAndWaitingDaysYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedOutput schema / properties / concepts / items / properties / nextStep
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / concepts / items / properties / status
      Added value: +{
      +  "type": "string"
      +}
    • changedOutput schema / properties / concepts / items / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "source",
      -  "target",
      -  "direction",
      -  "recordTypes",
      -  "savedAt",
      -  "openInAppUrl"
      -]New value: +[
      +  "id",
      +  "name",
      +  "source",
      +  "target",
      +  "direction",
      +  "status",
      +  "recordTypes",
      +  "savedAt",
      +  "openInAppUrl",
      +  "nextStep"
      +]
    • addedOutput schema / properties / integrations / items / properties / nextStep
      Added value: +{
      +  "default": null,
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / concepts
      Added value: +{
      +  "default": null,
      +  "items": {
      +    "properties": {
      +      "direction": {
      +        "type": "string"
      +      },
      +      "id": {
      +        "format": "uuid",
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "openInAppUrl": {
      +        "type": "string"
      +      },
      +      "recordTypes": {
      +        "items": {
      +          "type": "string"
      +        },
      +        "type": "array"
      +      },
      +      "savedAt": {
      +        "format": "date-time",
      +        "type": "string"
      +      },
      +      "source": {
      +        "properties": {
      +          "key": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "key",
      +          "name"
      +        ],
      +        "type": "object"
      +      },
      +      "target": {
      +        "properties": {
      +          "key": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "key",
      +          "name"
      +        ],
      +        "type": "object"
      +      }
      +    },
      +    "required": [
      +      "id",
      +      "name",
      +      "source",
      +      "target",
      +      "direction",
      +      "recordTypes",
      +      "savedAt",
      +      "openInAppUrl"
      +    ],
      +    "type": "object"
      +  },
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds scoping context — results are the signed-in customer's own integrations and include planned (not just active) concepts — but says nothing about result volume, ordering, or what an empty list means.

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

Conciseness5/5

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

Two sentences, no filler: the first front-loads the use condition and the returned payload, the second handles exclusions. The colon-separated field list is dense but readable and carries real routing value.

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

Completeness4/5

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

With zero params, full annotation coverage, and an output schema present, the definition covers everything an agent needs to select and call it. The field enumeration partially duplicates what the output schema already provides, which is the only small redundancy.

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

Parameters4/5

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

The tool takes no parameters, which is the baseline-4 case; there is nothing for the description to clarify. It correctly implies the implicit scoping to the signed-in customer rather than requiring a customer argument.

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 resource ('their own integrations') and enumerates exactly what each entry carries (id, systems, status, record types, last sync, failed/waiting records, next step, planned concepts), immediately separating it from the option- and health-oriented siblings.

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 states the triggering condition ('a signed in customer asks about their own integrations or a setup they planned') and explicitly names two exclusions with the correct alternative for each: get_integration_options for catalog/pricing questions and get_integration_health for failure diagnosis.

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.

Resources