Skip to main content
Glama

manage_connectors

Start a Dropbox or X connection, or disconnect accounts, for the targeted project. action=connect shows the Connect button in that project's ChatCut editor and returns its link. Nothing is connected yet: the user starts authorization there, then returns to this task; call list_connectors to continue.

Connecting never uploads or posts. action=disconnect removes accounts from ChatCut: call it only when the user explicitly asks to disconnect, and pass every account in targets as {platform, accountId, revision} from list_connectors (several, across platforms, in one call). If more than one account could be meant and the user did not say which, call list_connectors and ask first; never guess and never disconnect accounts they did not name. There is no disconnect-all, and nothing is disconnected in Plan mode. Each target is reported separately; a failure does not stop the others. Drafts and tasks bound to a disconnected account stop working; never move them to another account.

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_connectors"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesconnect: show the Connect button. disconnect: remove the accounts in targets; only when the user explicitly asked.
targetsNoWith disconnect: each account to remove, {platform, accountId, revision} from list_connectors. Name every one; there is no way to disconnect all.
platformNoWith connect: the platform to connect.
projectIdNoProject for this call (full ID or unambiguous prefix). Explicit-timeline calls never change the target of later calls; legacy project selection applies otherwise.
timelineIdNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Well beyond the annotations, it discloses that connecting never uploads or posts, that the initial connect only surfaces a button and the user must authorize externally, that each target is reported separately and one failure does not stop others, and that drafts/tasks bound to a disconnected account stop working. The one tension is that destructiveHint=false understates 'removes accounts' with breakage of bound drafts; the description does not address this, though it remains recoverable by re-authorization rather than a hard contradiction.

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?

Purpose is front-loaded in sentence one, then connect flow, then disconnect rules — a sensible ordering with no filler. There is mild redundancy in 'never guess and never disconnect accounts they did not name' restating the earlier 'only when the user explicitly asks', but the extra emphasis is defensible for a removal action.

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?

With no output schema, the description still tells the agent what connect returns (a link and a button in the project's editor) and what disconnect returns at a per-target level, and it covers the multi-call workflow with list_connectors. For a 5-parameter, two-action tool with side effects, nothing essential to correct invocation is missing.

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?

Schema coverage is 80%, so the baseline is 3; the description earns more by explaining the data dependency behind targets — the {platform, accountId, revision} triple must come from list_connectors, every account must be named, and several accounts across platforms go in one call. That constraint is not inferable from the schema alone. It says nothing about projectId/timelineId sizing or prefix semantics, which the schema still carries.

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 opening sentence names both specific operations and the resource: 'Start a Dropbox or X connection, or disconnect accounts, for the targeted project.' The two-action enum is spelled out and each branch is described concretely ('action=connect shows the Connect button... returns its link' vs. 'action=disconnect removes accounts'), so an agent can distinguish it from list_connectors and from the other manage_* siblings without opening 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 Guidelines5/5

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

It states when to use each action and the guardrails around them: disconnect only when the user explicitly asks, call list_connectors to continue after connect, and call list_connectors and ask when the target account is ambiguous. It also names exclusions explicitly — 'no disconnect-all' and 'nothing is disconnected in Plan mode' — plus the routing rule to list_connectors, which is the correct alternative.

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.