Skip to main content
Glama
hermoso-ai

Hermoso

Official
by hermoso-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Choose which accounts a brand may use

set_connector_accounts
DestructiveIdempotent

Specify which accounts a profile can post to and spend from for a connector. Replaces current selection; 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, 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. Free.

Input Schema

TableJSON 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.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"
  2. 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"
+]
  3. Addedv0.1.161

TDQS

A4.3/5.0
Behavior5/5

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

Annotations declare destructiveHint=true and idempotentHint=true, but the description adds real substance: the operation REPLACES the selection, omitted ids are un-shared, an empty list shares nothing and publishing then fails closed, and the server re-verifies every id against the live connection so unreachable ids are rejected. That is precisely the behavioral detail an agent needs for a destructive setter.

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 core content is front-loaded and dense, but the trailing list of all 25 providers duplicates the enum already present in the input schema verbatim, and the lone 'Free' token adds little. Redundancy with structured data costs it here.

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 needed and annotations covering safety hints, the description still supplies replacement semantics, fail-closed behavior, id validation, and account-type examples. An agent has everything required to call it correctly and safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so both parameters are already documented, including the empty-array semantics. The description only adds provenance ('ids from list_connector_accounts') and restates the empty-list rule, so the baseline of 3 applies.

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 (set) plus resource (connector accounts) and scope (which accounts a profile may post to and spend from), then enumerates concrete account types like Facebook Pages, Google Ads customers, and LinkedIn company Pages. An agent can distinguish it from siblings like list_connector_accounts and connect_connector without opening any schema.

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?

Points the agent to list_connector_accounts as the id source and instructs 'Ask the user which accounts they mean; posting as the wrong Page is a public mistake.' It gives clear usage context but names no explicit alternative for the setting operation or a when-not-to-use condition.

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