nango-mcp-server

Overview Schema Source Related Servers Discussions Admin

refresh_connection_credentials

Refresh OAuth credentials for a connection to obtain updated token status without exposing secrets. Use to resolve expired or invalid tokens.

Instructions

Force an OAuth refresh and return only a non-secret credential summary.

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": {
      "environment": "<environment>",
      "connectionId": "<connectionId>",
      "providerConfigKey": "<providerConfigKey>"
    },
    "name": "refresh_connection_credentials"
  }
}

Input Schema

Name	Required	Description	Default
`environment`	Yes
`connectionId`	Yes
`providerConfigKey`	Yes

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv2.0.0Aug 29, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / connectionId

Added value: +{
+  "title": "Connectionid",
+  "type": "string"
+}

removedInput schema / properties / connection_id

Removed value: -{
-  "title": "Connection Id",
-  "type": "string"
-}

addedInput schema / properties / providerConfigKey

Added value: +{
+  "title": "Providerconfigkey",
+  "type": "string"
+}

removedInput schema / properties / provider_config_key

Removed value: -{
-  "title": "Provider Config Key",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "environment",
-  "connection_id",
-  "provider_config_key"
-]New value: +[
+  "environment",
+  "connectionId",
+  "providerConfigKey"
+]

Addedv1.0.0Aug 25, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden and does disclose the mutating nature ('Force') and the restricted output ('non-secret'), which is useful. However, it says nothing about side effects such as token invalidation, required permissions, rate limits, or failure behavior, leaving meaningful behavioral uncertainty.

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?

One tight sentence with no filler, front-loaded with the action verb. Every word contributes meaning without redundancy.

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

Completeness2/5

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

An output schema exists, so return-value details are partially covered, but the description omits parameter semantics and all usage conditions. For a mutating tool with no annotations, this is too sparse to safely invoke, especially given 27 sibling tools.

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

Parameters1/5

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

The schema description coverage is 0% and the description provides no explanation of the three required parameters (environment, connectionId, providerConfigKey). An agent must guess their meanings purely from parameter names, which is inadequate for reliable invocation.

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 uses a specific verb phrase 'Force an OAuth refresh' and identifies the precise resource (connection credentials). It further distinguishes the tool from siblings by specifying the narrowed output ('non-secret credential summary'), which clearly separates it from read-only tools like get_connection.

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

Usage Guidelines2/5

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

No guidance is given on when to use this tool versus alternatives. The description states what it does but not when a refresh is appropriate, what prerequisites exist, or how this differs from related tools like get_connection or create_reconnect_session.

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