Skip to main content
Glama
Hermoso

Hermoso

Official

Choose which accounts a brand may use

set_connector_accounts
DestructiveIdempotent

Select which connected accounts a profile can publish to and spend from; this replaces the current selection, and an empty list shares nothing.

Instructions

Set WHICH of a connector's accounts this profile is allowed to post to and spend from — Facebook Pages / Instagram / Meta ad accounts, Google Ads customers, LinkedIn company Pages (and the personal profile), Pinterest or Microsoft Advertising ad accounts. Pass ids from list_connector_accounts. This REPLACES the current selection: anything you leave out is un-shared, and an EMPTY list shares nothing (publishing then refuses — it fails closed by design, and the server re-verifies every id against the live connection, so an id the account cannot actually reach is rejected rather than saved). Ask the user which accounts they mean; posting as the wrong Page is a public mistake. Providers: tiktok, x, youtube, threads, bluesky, telegram, pinterest, instagram, meta, google_ads, linkedin, pinterest_ads, linkedin_ads, reddit_ads, apple_ads, amazon_ads, microsoft_ads, google_business, google_analytics, snapchat_ads, x_ads, tiktok_ads, google_tag_manager, google_search_console, bing_webmaster. Free.

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>",
      "accountIds": "<accountIds>"
    },
    "name": "set_connector_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYeswhich connector to scope
accountIdsYesthe ids (from list_connector_accounts) this profile may use — an empty array shares nothing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.539
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "tiktok",
      -  "x",
      -  "youtube",
      -  "threads",
      -  "bluesky",
      -  "telegram",
      -  "pinterest",
      -  "instagram",
      -  "meta",
      -  "google_ads",
      -  "linkedin",
      -  "pinterest_ads",
      -  "linkedin_ads",
      -  "reddit_ads",
      -  "apple_ads",
      -  "microsoft_ads",
      -  "google_business",
      -  "google_analytics",
      -  "snapchat_ads",
      -  "x_ads",
      -  "tiktok_ads",
      -  "google_tag_manager",
      -  "google_search_console",
      -  "bing_webmaster"
      -]New value: +[
      +  "tiktok",
      +  "x",
      +  "youtube",
      +  "threads",
      +  "bluesky",
      +  "telegram",
      +  "pinterest",
      +  "instagram",
      +  "meta",
      +  "google_ads",
      +  "linkedin",
      +  "pinterest_ads",
      +  "linkedin_ads",
      +  "reddit_ads",
      +  "apple_ads",
      +  "amazon_ads",
      +  "microsoft_ads",
      +  "google_business",
      +  "google_analytics",
      +  "snapchat_ads",
      +  "x_ads",
      +  "tiktok_ads",
      +  "google_tag_manager",
      +  "google_search_console",
      +  "bing_webmaster"
      +]
  2. Changed1 schema field changedv0.1.519
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "tiktok",
      -  "x",
      -  "youtube",
      -  "threads",
      -  "bluesky",
      -  "telegram",
      -  "reddit",
      -  "pinterest",
      -  "instagram",
      -  "meta",
      -  "google_ads",
      -  "linkedin",
      -  "pinterest_ads",
      -  "linkedin_ads",
      -  "reddit_ads",
      -  "apple_ads",
      -  "microsoft_ads",
      -  "google_business",
      -  "google_analytics",
      -  "snapchat_ads",
      -  "x_ads",
      -  "tiktok_ads",
      -  "google_tag_manager",
      -  "google_search_console",
      -  "bing_webmaster"
      -]New value: +[
      +  "tiktok",
      +  "x",
      +  "youtube",
      +  "threads",
      +  "bluesky",
      +  "telegram",
      +  "pinterest",
      +  "instagram",
      +  "meta",
      +  "google_ads",
      +  "linkedin",
      +  "pinterest_ads",
      +  "linkedin_ads",
      +  "reddit_ads",
      +  "apple_ads",
      +  "microsoft_ads",
      +  "google_business",
      +  "google_analytics",
      +  "snapchat_ads",
      +  "x_ads",
      +  "tiktok_ads",
      +  "google_tag_manager",
      +  "google_search_console",
      +  "bing_webmaster"
      +]
  3. Changed1 schema field changedv0.1.374
    • changedInput schema / properties / accountIds / description
      Previous value: -"the ids (from list_connector_accounts) this brand may use — an empty array shares nothing"New value: +"the ids (from list_connector_accounts) this profile may use — an empty array shares nothing"
  4. Changed1 schema field changedv0.1.189
    • changedInput schema / properties / provider / enum
      Previous value: -[
      -  "meta",
      -  "google_ads",
      -  "linkedin",
      -  "pinterest_ads",
      -  "linkedin_ads",
      -  "reddit_ads",
      -  "apple_ads",
      -  "microsoft_ads",
      -  "google_business",
      -  "google_analytics",
      -  "snapchat_ads",
      -  "x_ads",
      -  "tiktok_ads",
      -  "google_tag_manager",
      -  "google_search_console",
      -  "bing_webmaster"
      -]New value: +[
      +  "tiktok",
      +  "x",
      +  "youtube",
      +  "threads",
      +  "bluesky",
      +  "telegram",
      +  "reddit",
      +  "pinterest",
      +  "instagram",
      +  "meta",
      +  "google_ads",
      +  "linkedin",
      +  "pinterest_ads",
      +  "linkedin_ads",
      +  "reddit_ads",
      +  "apple_ads",
      +  "microsoft_ads",
      +  "google_business",
      +  "google_analytics",
      +  "snapchat_ads",
      +  "x_ads",
      +  "tiktok_ads",
      +  "google_tag_manager",
      +  "google_search_console",
      +  "bing_webmaster"
      +]
  5. Addedv0.1.161

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the mutation profile is known. The description adds genuinely non-obvious behavior beyond that: full replacement semantics, empty list failing closed, and server-side re-verification of every id against the live connection rejecting unreachable ids. Strong added context, but it does not describe reversibility of a prior selection or how to recover it.

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 destructive/replacement warning is front-loaded and emphasized well, and the parenthetical about live re-verification is high-value. However, the full provider list restates the schema enum word for word and consumes substantial space without earning it, and "Free." is orphaned.

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 destructive, two-parameter scoping tool with no output schema, the definition covers the prerequisite tool, the replacement semantics, the empty-list fail-closed case, and the validation failure mode. An agent has everything needed to call it correctly and to warn the user about consequences.

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; the description adds real meaning by specifying that ids must come from list_connector_accounts and that an empty array results in publishing refusing to run. The verbatim enumeration of all 25 providers duplicates the schema enum and adds nothing.

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?

"Set WHICH of a connector's accounts this profile is allowed to post to and spend from" states a specific verb, resource, and scope, and names the concrete account types involved (Facebook Pages, Google Ads customers, LinkedIn Pages). It is immediately distinguishable from list_connector_accounts, which the description calls out as the source of ids.

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 a clear precondition and alternative — "Pass ids from list_connector_accounts" — plus a human-in-the-loop instruction to confirm with the user before posting as the wrong Page. It lacks an explicit statement of when not to call this tool (e.g., read-only inspection), but the operating context is otherwise unambiguous.

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