Skip to main content
Glama
Hermoso

Hermoso

Official

Remove my own account from a shared connection

leave_connector
DestructiveIdempotent

Remove only your own account from a shared multi-contributor connection, so teammates keep working while your credential and shared access are dropped. Use instead of disconnect_connector.

Instructions

On a connector that several teammates can contribute their OWN account to (see list_connectors — the row reports multiContributor), remove YOURS from this profile: your stored credential is dropped and the accounts you shared stop being shared. Your teammates' accounts on the same connection keep working, and nothing changes at the provider — reconnecting in a browser shares again. Use this instead of disconnect_connector when the connection is not yours to remove: disconnect_connector removes the whole connection for everyone on this profile, and only the person who created the connection may call it.

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": {
      "provider": "<provider>"
    },
    "name": "leave_connector"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYesprovider id exactly as list_connectors reports it, e.g. "linkedin", "tiktok_ads", "meta"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.161

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructive/idempotent/openWorld, and the description goes well beyond them: it names exactly what is destroyed (the stored credential and the shared accounts), what is preserved (teammates' accounts keep working), and what is recoverable (nothing changes at the provider; reconnecting in a browser re-shares). That is the precise collateral-damage profile an agent needs before firing a destructive call.

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?

The key scope and the sibling routing are front-loaded, and nearly every clause carries real information. The passage is dense, using nested colons and em-dashes, so it takes a careful read, but there is no filler to cut.

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?

For a one-parameter destructive mutation with no output schema, the definition covers eligibility, blast radius, team impact, reversibility, and the correct alternative; nothing an agent needs to call this safely 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 100% and the single provider parameter is well documented in the schema, so baseline is 3; the description adds value by pointing the agent at list_connectors as the authoritative source for the provider id and by qualifying which connectors are eligible (multiContributor).

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?

States a specific verb and resource ("remove YOURS from this profile" on a multi-contributor connector) and immediately scopes it against the sibling that does something similar, so the agent can tell leave_connector from disconnect_connector without opening either 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?

Gives an explicit when-to-use rule ("Use this instead of disconnect_connector when the connection is not yours to remove") plus the prerequisite condition (connector must allow multiple contributors, check the multiContributor row via list_connectors) and the constraint on the alternative (only the creator may call disconnect_connector).

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

Deploy Server

Other Tools