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
Idempotent

Set the connector accounts a brand may post to and spend from, replacing the current selection. Omitted accounts are un-shared; an empty list disables all publishing.

Instructions

Set WHICH of a connector's accounts this brand 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 brand may use — an empty array shares nothing

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.7/5.0
Behavior1/5

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

The description is behaviorally rich: it discloses replacement semantics, fail-closed behavior, server-side id verification, and the public risk of posting as the wrong Page. However, it directly contradicts the annotation destructiveHint=false by stating that the tool REPLACES the current selection and un-shares any omitted accounts. Because the annotation marks the operation as non-destructive while the description explicitly describes an overwriting/un-sharing side effect, this is an annotation contradiction.

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 core purpose and critical warning are clearly front-loaded, and each major behavioral point earns its place. However, the provider enum is duplicated verbatim from the input schema, and the trailing 'Free.' adds no decision-making value, so it is not maximally concise.

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?

For a two-parameter configuration tool with no output schema, the description is nearly complete: it covers required inputs, replacement side effects, empty-list behavior, server validation, failure semantics, and user confirmation. The only minor gap is that it never describes what the API returns on success or failure, though that is less critical for a setter tool.

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 meaningful context by explaining what the ids represent (Facebook Pages, Instagram accounts, Google Ads customers, etc.), framing them as 'allowed to post to and spend from,' and reiterating the empty-array-means-share-nothing behavior. This goes modestly beyond the schema.

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 description states a specific verb ('Set') and resource ('which of a connector's accounts this brand is allowed to post to and spend from'), and distinguishes the operation from read-only siblings like list_connector_accounts by naming it as the id source. It also makes the brand-scoping intent unmistakable.

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?

The description gives a clear prerequisite and workflow: pass ids from list_connector_accounts, ask the user which accounts they mean, and understand that an empty list shares nothing. It does not explicitly compare against alternative setter tools, but the usage context is specific enough to route an agent correctly.

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