Skip to main content
Glama
Hermoso

Hermoso

Official

Connect a paste-a-key account

connect_connector
DestructiveIdempotent

Connect key-based provider accounts without a browser: pass provider fields, validate the key live, and save; OAuth-only accounts get a sign-in link.

Instructions

Connect an account that links with a KEY rather than a sign-in screen, from here, with no browser: AppLovin Ads, Stripe, Intercom, Mailchimp, Any mailbox, Klaviyo, Vercel, ChatGPT Ads, Apple Ads, Bluesky, Telegram, Bing Webmaster Tools, PostHog, Mixpanel, Amplitude, LINE, WordPress, Webflow, Wix, Slack, Discord, Webhook. Pass provider and fields in that provider's own field names (listed below, * = required). The key is checked live with the provider before anything is saved, exactly as the app's Connectors page checks it, and the reply is read back from the saved connection. OFFER BOTH WAYS AND LET THE USER CHOOSE: a key pasted into this chat stays in this conversation's history, while pasting it in the app (Connectors, or the one-click link https://app.hermoso.ai/?connect=) keeps it out of the chat. Hermoso never repeats a submitted key back. An account that connects through the provider's own sign-in screen (OAuth) cannot be connected here: this answers with the link to hand the user instead. Apple Ads with no key material first generates a signing key pair and returns the public key to register with Apple plus a setupToken to send back. Fields: applovin_ads {reportKey, eventKey, apiKey, capiKey, accountId} · stripe {apiKey*} · intercom {accessToken*, region} · mailchimp {apiKey*, server} · smtp {email*, password*, preset, username, smtpHost, smtpPort, smtpSecurity, imapHost, imapPort, imapSecurity, fromName} · klaviyo {apiKey*} · vercel {token*, team} · openai_ads {apiKey*} · apple_ads {clientId, teamId, keyId, privateKey, setupToken, orgId} · bluesky {identifier*, appPassword*, pds} · telegram {token*} · bing_webmaster {apiKey*} · posthog {apiKey*, region, host, projectId} · mixpanel {username*, secret*, projectId*, region, workspaceId} · amplitude {apiKey*, secretKey*, region, host} · line {channelAccessToken*, channelSecret*, replaceWebhook} · wordpress {siteUrl*, username*, appPassword*} · webflow {token*, siteId, collectionId} · wix {apiKey*, siteId*, memberId} · slack {webhookUrl, announceWebhookUrl} · discord {webhookUrl, announceWebhookUrl} · webhook {webhookUrl*}.

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": "connect_connector"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNothat provider's own field names and values, e.g. {"apiKey":"…"}; the names for each provider are in the description
providerYesthe connector id: applovin_ads, stripe, intercom, mailchimp, smtp, klaviyo, vercel, openai_ads, apple_ads, bluesky, telegram, bing_webmaster, posthog, mixpanel, amplitude, line, wordpress, webflow, wix, slack, discord, webhook

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.571
    • changedInput schema / properties / provider / description
      Previous value: -"the connector id: applovin_ads, stripe, intercom, mailchimp, klaviyo, vercel, openai_ads, apple_ads, bluesky, telegram, bing_webmaster, posthog, mixpanel, amplitude, wordpress, slack, discord, webhook"New value: +"the connector id: applovin_ads, stripe, intercom, mailchimp, smtp, klaviyo, vercel, openai_ads, apple_ads, bluesky, telegram, bing_webmaster, posthog, mixpanel, amplitude, line, wordpress, webflow, wix, slack, discord, webhook"
  2. Changed1 schema field changedv0.1.519
    • changedInput schema / properties / provider / description
      Previous value: -"the connector id: applovin_ads, stripe, intercom, vercel, openai_ads, apple_ads, bluesky, telegram, bing_webmaster, posthog, mixpanel, amplitude, slack, discord, webhook"New value: +"the connector id: applovin_ads, stripe, intercom, mailchimp, klaviyo, vercel, openai_ads, apple_ads, bluesky, telegram, bing_webmaster, posthog, mixpanel, amplitude, wordpress, slack, discord, webhook"
  3. Changed1 schema field changedv0.1.435
    • changedInput schema / properties / provider / description
      Previous value: -"the connector id: applovin_ads, stripe, vercel, openai_ads, apple_ads, bluesky, telegram, bing_webmaster, posthog, mixpanel, amplitude, slack, discord, webhook"New value: +"the connector id: applovin_ads, stripe, intercom, vercel, openai_ads, apple_ads, bluesky, telegram, bing_webmaster, posthog, mixpanel, amplitude, slack, discord, webhook"
  4. Changed1 schema field changedv0.1.410
    • changedInput schema / properties / provider / description
      Previous value: -"the connector id: applovin_ads, stripe, openai_ads, apple_ads, bluesky, telegram, bing_webmaster, posthog, mixpanel, amplitude, slack, discord, webhook"New value: +"the connector id: applovin_ads, stripe, vercel, openai_ads, apple_ads, bluesky, telegram, bing_webmaster, posthog, mixpanel, amplitude, slack, discord, webhook"
  5. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / provider / description
      Previous value: -"the connector id: stripe, openai_ads, apple_ads, bluesky, telegram, bing_webmaster, posthog, mixpanel, amplitude, slack, discord, webhook"New value: +"the connector id: applovin_ads, stripe, openai_ads, apple_ads, bluesky, telegram, bing_webmaster, posthog, mixpanel, amplitude, slack, discord, webhook"
  6. Addedv0.1.243

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations it discloses that the key is validated live with the provider before anything is saved, that the response is read back from the saved connection, that submitted keys are never echoed back, and the Apple Ads key-pair/setupToken special case. It does not explain what destructiveHint=true means here — e.g. whether reconnecting an already-connected provider replaces or overwrites the existing connection — which is the main remaining behavioral gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is well front-loaded, but the body is a dense ~200-word block that mixes routing guidance, secret-handling policy, an Apple Ads exception, and a long inline field dump. The field table is necessary content, yet its inline placement makes the paragraph harder to scan than a short prose section plus structured listing would be.

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?

With no output schema, the description still tells the agent what comes back (the saved connection read back, or a setup link for OAuth providers, or a public key plus setupToken for Apple Ads), which is the key completeness need. The only shortfall is that per-provider field meanings and the overwrite behavior of reconnecting are not covered.

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%, so the baseline is 3, but the description goes further by enumerating each provider's field names with '*' required markers and listing the optional extras (region, host, preset, team, siteId, setupToken). The `fields` object is free-form with no internal schema, so this enumeration is genuinely load-bearing rather than repetition; it stops short of explaining what individual fields mean.

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 first sentence gives a specific verb (connect) and a precisely bounded resource class — accounts that authenticate with a key rather than an OAuth sign-in screen — and enumerates the supported providers. It also implicitly separates this tool from the OAuth path and from sibling management tools by stating the credential model rather than just 'connector'.

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 both when to use it (key-based providers, no browser available) and when not to (OAuth accounts, which return a link to hand the user instead), plus an explicit instruction to offer the in-chat and in-app paths and let the user choose. That is a full when/when-not/alternative triad with a stated privacy trade-off driving the choice.

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