Skip to main content
Glama
Hermoso

Hermoso

Official

List connectors

list_connectors
Read-onlyIdempotent

Lists connected third-party accounts, provider status and labels, plus available providers, and flags outdated permissions that can cause provider refusals; reconnect in the browser to renew consent.

Instructions

List the third-party accounts connected to this workspace (Meta, Google Ads, Google Drive/Sheets/Docs, YouTube, LinkedIn, OneDrive, Slack, …) — provider, status and the connected account label — PLUS which providers are available to connect. IT ALSO FLAGS A CONNECTION WHOSE PERMISSIONS ARE OUT OF DATE: a provider writes its granted permission set into the token at consent time, so a connection authorized before a permission was approved does not carry it and never will — those calls are refused by the provider and no retry or wait can change it. Check this FIRST when a connected provider starts refusing things. The fix is a browser: the user reconnects under Connectors. Read-only, free.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_connectors"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.161

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent annotations by explaining the stale-permission mechanism (permissions are baked into the token at consent time), why retry or waiting cannot fix it, and that remediation requires a browser reconnect by the user. It also discloses the returned fields and adds 'free' (no credit cost), which the annotations do not convey. Safety hints are restated but the added diagnostic context is substantial.

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?

Front-loaded with what is listed, then the diagnostic caveat, then the remedy and cost — a sensible order with no filler sentences. The all-caps emphasis and the em-dash-heavy run-on are stylistically heavy, and 'Read-only, free' partly duplicates the annotations, keeping it short of a 5.

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 parameters, no output schema, and annotations already covering safety, the description carries the remaining burden well: it enumerates what comes back, explains the failure mode it detects, and states the user-side fix. An agent has everything needed to call it and interpret the result.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description instead spends its space on output semantics, which is appropriate here.

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?

States a specific verb and resource ('List the third-party accounts connected to this workspace') and enumerates the providers and returned fields (provider, status, account label) plus the second facet of available-to-connect providers. It is clear on its own, but it never distinguishes itself from the very close sibling list_connector_accounts, so an agent must still infer which one to call.

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

Usage Guidelines4/5

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

Gives an explicit, memorable trigger: 'Check this FIRST when a connected provider starts refusing things,' which tells the agent when to reach for this tool during troubleshooting. It does not state when NOT to use it or name an alternative for the narrower account-listing case, so the routing guidance is clear but incomplete.

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