Skip to main content
Glama
Hermoso

Hermoso

Official

List a connector’s accounts

list_connector_accounts
Read-onlyIdempotent

Lists every account identity available for a provider and shows which ones the current profile may use, so users can choose valid posting or ad accounts before assigning connectors.

Instructions

Show every identity a connected account can act as, and which ones this PROFILE is currently allowed to use — Facebook Pages + Instagram + Meta ad accounts, Google Ads customers, LinkedIn company Pages (and the personal profile), Pinterest ad accounts, Microsoft Advertising accounts. One person often administers several; only the ticked ones can be posted to or spent from. Call this before set_connector_accounts, and let the USER pick — never guess. 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. Read-only, 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>"
    },
    "name": "list_connector_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
providerYeswhich connector’s accounts to list

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

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'Read-only, free' mostly restates what the agent already knows. The description does add value beyond annotations by explaining the semantics of the result: one person often administers several accounts, and only the ticked ones can be posted to or spent from. It says nothing about pagination, ordering, or how large the list can get.

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?

Purpose and the sequencing rule are front-loaded, which is good. However, the long comma-separated provider list duplicates the schema enum almost exactly and consumes a large share of the text without adding information, so the description is longer than it needs to 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?

There is no output schema, but the description conveys the shape of the return adequately: a set of identities plus which ones are permitted. Given a one-parameter read tool, that is close to sufficient; only pagination and result volume are unaddressed.

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 coverage is 100% and the single provider parameter has a full enum, so the schema already does the work. The description reprints the same 25-provider list verbatim, which adds redundancy rather than new meaning, though it does confirm the parameter selects which connector's accounts are returned.

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: it shows every identity a connected account can act as and which of those the profile may currently use. It enumerates the kinds of identities (Facebook Pages, Google Ads customers, LinkedIn Pages, etc.), so an agent knows what comes back. It does not distinguish itself from narrower siblings such as list_meta_pages or list_pinterest_boards, which is the only thing keeping it from a 5.

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?

Explicitly says to call this before set_connector_accounts and to let the USER pick — never guess, which is real, actionable sequencing guidance. It does not state when to prefer a provider-specific lister instead, so it is clear context without exclusions.

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