Skip to main content
Glama

List ad accounts

ads_list_accounts
Read-only

List the ad accounts an ads connection can reach: Meta ad accounts (act_), directly or through a Business portfolio, or TikTok advertisers () for a tiktok_ads account. Every other ads tool takes an adAccountId from here.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ads_list_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNometa_ads, tiktok_ads or linkedin_ads. Needed only when the profile has more than one ad network and no accountId is given.
accountIdNoThe Facebook accountId from list_accounts. Without it, pass profileId to use that profile's Facebook connection.
profileIdNoA profileId from list_profiles. Optional when accountId is given, which names its profile; if both are given they must agree.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / platform / description
      Previous value: -"meta_ads or tiktok_ads. Needed only when the profile has both ad networks and no accountId is given."New value: +"meta_ads, tiktok_ads or linkedin_ads. Needed only when the profile has more than one ad network and no accountId is given."
    • changedInput schema / properties / platform / enum
      Previous value: -[
      -  "meta_ads",
      -  "tiktok_ads"
      -]New value: +[
      +  "meta_ads",
      +  "tiktok_ads",
      +  "linkedin_ads"
      +]
  2. Changed1 schema field changed
    • addedInput schema / properties / platform
      Added value: +{
      +  "description": "meta_ads or tiktok_ads. Needed only when the profile has both ad networks and no accountId is given.",
      +  "enum": [
      +    "meta_ads",
      +    "tiktok_ads"
      +  ],
      +  "type": "string"
      +}
  3. Changed2 schema fields changed
    • changedInput schema / properties / accountId / description
      Previous value: -"The Facebook accountId from list_accounts. Defaults to the profile's Facebook connection."New value: +"The Facebook accountId from list_accounts. Without it, pass profileId to use that profile's Facebook connection."
    • changedInput schema / properties / profileId / description
      Previous value: -"Defaults to the profile your API key is bound to."New value: +"A profileId from list_profiles. Optional when accountId is given, which names its profile; if both are given they must agree."
  4. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds one useful behavioral fact beyond that — accounts may be reached 'directly or through a Business portfolio' — but says nothing about pagination, whether results are cached, or what happens when the connection lacks a given network.

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?

Two tight sentences with the resource and platform formats front-loaded, then the downstream-consumption rule. Slightly marred because the platform enumeration in the first sentence names only Meta and TikTok while the schema enum also includes linkedin_ads, leaving the sentence asymmetrical with its own parameter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter read tool with no output schema, the description is mostly sufficient, and 'adAccountId from here' implies the returned ID field. However, the omission of LinkedIn (present in the platform enum) and the absence of any note on result shape or scope leave a real gap an agent would hit when the profile is LinkedIn-only.

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 all three parameters (platform, accountId, profileId) are already documented with their fallback rules, making 3 the baseline. The description adds no syntax or format guidance for these inputs, and its mention of 'act_<digits>' describes returned IDs rather than the parameters themselves.

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 and resource ('List the ad accounts an ads connection can reach') and pins down the concrete ID shapes returned per platform (act_<digits> for Meta, <digits> for TikTok). This lets an agent separate it from neighbors like ads_list_businesses, ads_get_account, and list_accounts 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?

The sentence 'Every other ads tool takes an adAccountId from here' is an explicit routing rule that tells the agent to call this first before any other ads tool. It does not state when NOT to use it (e.g., when an adAccountId is already known, or how it differs from ads_list_businesses), so it stops short of full when/when-not coverage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources