Retrieve all integrations configured in a Nango environment to review or manage your setup.
List integrations configured in one Nango environment.
| Name | Required | Description | Default |
|---|---|---|---|
| environment | Yes | ||
| refreshSecret | No |
Changes observed during successful MCP inspections.
v2.0.0Input schema / additionalPropertiesAdded value: +falseInput schema / properties / refreshSecretAdded value: +{
+ "default": false,
+ "title": "Refreshsecret",
+ "type": "boolean"
+}Input schema / properties / refresh_secretRemoved value: -{
- "default": false,
- "title": "Refresh Secret",
- "type": "boolean"
-}v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It states the listing action but omits any mention of the refreshSecret parameter's behavior, whether the operation is read-only, or what the return payload looks like. The refreshSecret flag could imply side effects or extra behavior that an agent would not anticipate.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single clear, front-loaded sentence with no filler. Every word earns its place and the core purpose is immediately visible.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with no output schema and no annotations, this description is too thin. It does not mention return structure, pagination, the meaning or effect of refreshSecret, or how this relates to sibling tools. An agent has enough to guess the basic purpose but not enough to call the tool with full confidence.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It indirectly adds meaning to 'environment' by saying integrations are configured in one Nango environment, but it says nothing about accepted values or format, and it completely omits the refreshSecret parameter and its semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('List'), resource ('integrations'), and scope ('configured in one Nango environment'). This clearly differentiates the tool from siblings like list_connections and list_environments, and from get_integration which targets a single integration.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description offers no guidance on when to choose this tool over alternatives such as get_integration, list_connections, or list_environments. No conditions, prerequisites, or exclusions are mentioned, leaving the agent to infer usage solely from the word 'List'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.