Skip to main content
Glama

Adeli

by com.tryadeli.app
OverviewDiscussionsAdmin

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.

Input Schema

NameRequiredDescriptionDefault
platformNometa_ads or tiktok_ads. Needed only when the profile has both ad networks 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. 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"
+}
  2. 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."
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to establish safety. It adds useful behavioral context by explaining that accounts may come directly from Meta or through a Business portfolio, that TikTok advertisers are returned for tiktok_ads, and that the returned IDs are inputs to all other ads tools.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences, front-loaded with the core action and account scope, followed by the critical downstream dependency. Every clause carries useful signal: account ID formats, portfolio access, TikTok distinction, and the adAccountId relationship.

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?

The definition is nearly complete for a read-only list tool: annotations cover safety, the schema fully covers parameters, and the description explains account scope and the returned ID's role in other tools. It does not describe return shape, pagination, or empty-result behavior, but those are minor gaps given the tool's simplicity and lack of an output schema.

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 the schema already documents platform, accountId, and profileId in detail, including enum values and ID formats. The description reinforces platform-specific account types but does not add parameter-level semantics beyond the schema, which is the baseline 3 case.

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 and resource: listing ad accounts reachable by an ads connection. It also clarifies the Meta and TikTok account ID formats and explains the downstream role of the returned adAccountId, making the tool distinguishable from broader siblings like list_accounts or ads_list_businesses.

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 clearly establishes when to use the tool: to obtain an adAccountId that every other ads tool consumes. It does not explicitly name alternatives or when-not-to-use cases, such as ads_list_businesses for portfolio-level exploration, so it falls short of a 5.

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

All Adeli toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources