Skip to main content
Glama
zernio-mcp
by Eyalm321

zernio_list_ad_accounts

Lists ad accounts across Meta, Google, TikTok, LinkedIn, X, Reddit, and Pinterest for a connected Zernio account, returning each account's ID and status.

Instructions

List the ad accounts (Meta, Google, TikTok, LinkedIn, X, Reddit, Pinterest) reachable through one connected Zernio account, with their IDs and status.

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": {
      "accountId": "<accountId>"
    },
    "name": "zernio_list_ad_accounts"
  }
}

Input Schema

NameRequiredDescriptionDefault
liveNotrue: list live from the platform instead of Zernio's stored catalog
limitNoMaximum number of ad accounts to return
accountIdYesThe Zernio account ID of the ads connection (from zernio_list_accounts)
adAccountIdNoReturn only this platform ad account (e.g. act_123 for Meta)
inScopeOnlyNotrue: only ad accounts this connection accepts as adAccountId on the other ads tools

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.3.1
    • addedInput schema / properties / accountId
      Added value: +{
      +  "description": "The Zernio account ID of the ads connection (from zernio_list_accounts)",
      +  "type": "string"
      +}
    • addedInput schema / properties / adAccountId
      Added value: +{
      +  "description": "Return only this platform ad account (e.g. act_123 for Meta)",
      +  "type": "string"
      +}
    • addedInput schema / properties / inScopeOnly
      Added value: +{
      +  "description": "true: only ad accounts this connection accepts as adAccountId on the other ads tools",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Maximum number of ad accounts to return",
      +  "maximum": 1000,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / live
      Added value: +{
      +  "description": "true: list live from the platform instead of Zernio's stored catalog",
      +  "type": "boolean"
      +}
    • addedInput schema / required
      Added value: +[
      +  "accountId"
      +]
  2. First observedv2.1.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does signal a read operation and discloses the return payload (IDs and status), but says nothing about authorization needs, pagination behavior with limit, or the difference in freshness between live and stored results beyond what the schema states.

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?

A single front-loaded sentence with the action, scope, platform coverage, and return contents; no filler or repetition.

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 five-parameter read-only list tool with fully documented schema and no output schema, the description covers purpose, scope, and return contents adequately. It stops short of explaining the live vs stored catalog distinction or pagination, but those gaps are covered by schema descriptions.

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%, with all five parameters documented in the schema, so the baseline is 3. The description adds only the framing that results are scoped to one connected account; it adds no meaning for live, limit, adAccountId, or inScopeOnly.

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?

Names a specific verb (List) and resource (ad accounts), scopes them to a single connected Zernio account, enumerates the supported platforms, and states what is returned (IDs and status). This is clearly distinct from the sibling zernio_list_accounts, which lists the Zernio accounts themselves.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is the discovery step for ad accounts tied to one connection, but the description never says when to prefer it over zernio_list_accounts or when to use the live/inScopeOnly flags. No exclusions or prerequisites (e.g. that accountId comes from zernio_list_accounts) appear in the description itself.

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