Skip to main content
Glama

Connected apps and keys

manage_connections
Destructive

Disconnect a connected app, revoke an API key or remove a webhook. Keys and webhooks are created in Settings › Agents & API. Actions: disconnect_agent, revoke_key, remove_webhook. Call with action "help" for each action's fields.

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": {
      "action": "<action>"
    },
    "name": "manage_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
key_idNoAn API key's id from get_connections list.
paramsNoFields for the action. Call with action "help" to list each action's fields.
grant_idNoA connected app's id from get_connections list.
webhook_idNoA webhook's id from get_connections list.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / action / enum
      Previous value: -[
      -  "list",
      -  "disconnect_agent",
      -  "revoke_key",
      -  "remove_webhook",
      -  "help"
      -]New value: +[
      +  "disconnect_agent",
      +  "revoke_key",
      +  "remove_webhook",
      +  "help"
      +]
    • changedInput schema / properties / grant_id / description
      Previous value: -"A connected app's id from manage_connections list."New value: +"A connected app's id from get_connections list."
    • changedInput schema / properties / key_id / description
      Previous value: -"An API key's id from manage_connections list."New value: +"An API key's id from get_connections list."
    • changedInput schema / properties / webhook_id / description
      Previous value: -"A webhook's id from manage_connections list."New value: +"A webhook's id from get_connections list."
  2. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds the action enumeration and the 'help' escape hatch, but does not state consequences of revocation (e.g., an agent or app losing access immediately, irreversibility, or downstream effects). Against strong annotations, this is adequate but not rich.

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?

Two compact sentences front-load the destructive actions, followed by a short invocation note. No filler, though the mention of where keys are created is slightly tangential relative to the core removal purpose.

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?

For a five-parameter dispatcher with a nested free-form params object and no output schema, the description covers the action set and provides the 'help' mechanism for discovering per-action fields. What remains unstated—return values and post-revocation effects—is modest given the help affordance and the destructive annotation.

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 80%, so per-parameter descriptions already explain key_id, grant_id, and webhook_id. The description only adds 'Call with action "help" for each action's fields', which is an invocation hint rather than semantics; it does not map which id parameter belongs to which action or explain the free-form params object beyond the schema's own text. Baseline 3 is appropriate.

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

Purpose4/5

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

The description names three specific verb+resource pairs (disconnect_agent, revoke_key, remove_webhook) so an agent knows exactly what mutation happens. It also clarifies that keys and webhooks are created elsewhere (Settings › Agents & API), implying this tool only removes them. It stops short of explicitly contrasting with the read-side sibling get_connections, which only appears in the schema.

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

Usage Guidelines3/5

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

Usage is implied by the action names, and 'Keys and webhooks are created in Settings › Agents & API' hints that creation is not handled here. There is no explicit when-to-use/when-not-to-use guidance, no prerequisites (e.g., ownership or admin requirements), and no pointer to get_connections as the way to obtain the required ids.

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.