Skip to main content
Glama

Trillboards DOOH Advertising

by io.github.snehdhruv
OverviewDiscussionsAdmin

list_accounts

[AdCP Accounts] List the accounts this credential can transact on.

This seller's account model is 'explicit': one API key IS one account, so this returns exactly one account — the partner behind the key. Use it to discover your account_id before any account-scoped call, and to confirm the account's status before you buy.

WHEN TO USE:

  • Discovering the account_id to pass to account-scoped tasks

  • Checking your account is 'active' before creating a media buy

  • Introspecting what your key is permitted to do (accounts[].authorization.allowed_tasks)

RETURNS:

  • accounts: AdCP Account objects (account_id, name, status, operator, brand, billing, account_scope) plus an authorization object naming the tasks this key may invoke

  • pagination: has_more is always false — one credential, one account

EXAMPLE: list_accounts({}) list_accounts({ status: "active" })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by account status. Omit to return the account in any status.
accountNoExact account filter. Either account_id, or the natural key (brand.domain + operator). Returns empty when it does not match this credential's account — which is how you confirm the key you hold is the one you meant.
contextNo
sandboxNoFilter by sandbox status — matched against the account's real state, not a stub. A sandbox account validates a buy exactly as a live one does (same errors, same codes) but books no placements and marks every response sandbox: true, so it is safe to exercise end to end. Sandbox is our classification, not buyer-settable: ask for a sandbox credential rather than sending sandbox on a live key.
paginationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
  2. Changed3 schema fields changed
    • removedInput schema / properties / adcp_major_version
      Removed value: -{
-  "description": "Legacy major-precision AdCP version pin, an integer (e.g. 3), carried since 3.0. Prefer adcp_version. A major this agent does not speak is answered with a VERSION_UNSUPPORTED task failure; get_adcp_capabilities.adcp.major_versions lists the supported set.",
-  "type": "integer"
-}
    • removedInput schema / properties / adcp_version
      Removed value: -{
-  "description": "Release-precision AdCP version this request is pinned to, \"MAJOR.RELEASE\" (e.g. \"3.1\"). A release this agent does not speak is answered with a VERSION_UNSUPPORTED task failure listing the ones it does. Read get_adcp_capabilities.adcp.supported_versions to pin correctly.",
-  "type": "string"
-}
    • removedInput schema / properties / context / description
      Removed value: -"Opaque caller-supplied correlation object. Echoed back byte-for-byte, unparsed, on both successful and failed responses; the agent never reads its contents."
  3. Changed3 schema fields changed
    • addedInput schema / properties / adcp_major_version
      Added value: +{
+  "description": "Legacy major-precision AdCP version pin, an integer (e.g. 3), carried since 3.0. Prefer adcp_version. A major this agent does not speak is answered with a VERSION_UNSUPPORTED task failure; get_adcp_capabilities.adcp.major_versions lists the supported set.",
+  "type": "integer"
+}
    • addedInput schema / properties / adcp_version
      Added value: +{
+  "description": "Release-precision AdCP version this request is pinned to, \"MAJOR.RELEASE\" (e.g. \"3.1\"). A release this agent does not speak is answered with a VERSION_UNSUPPORTED task failure listing the ones it does. Read get_adcp_capabilities.adcp.supported_versions to pin correctly.",
+  "type": "string"
+}
    • addedInput schema / properties / context / description
      Added value: +"Opaque caller-supplied correlation object. Echoed back byte-for-byte, unparsed, on both successful and failed responses; the agent never reads its contents."
  4. Changed3 schema fields changed
    • addedInput schema / properties / account / description
      Added value: +"Exact account filter. Either account_id, or the natural key (brand.domain + operator). Returns empty when it does not match this credential's account — which is how you confirm the key you hold is the one you meant."
    • addedInput schema / properties / sandbox / description
      Added value: +"Filter by sandbox status — matched against the account's real state, not a stub. A sandbox account validates a buy exactly as a live one does (same errors, same codes) but books no placements and marks every response sandbox: true, so it is safe to exercise end to end. Sandbox is our classification, not buyer-settable: ask for a sandbox credential rather than sending sandbox on a live key."
    • addedInput schema / properties / status / description
      Added value: +"Filter by account status. Omit to return the account in any status."
  5. Added

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the key model (one credential, one account), guarantees exactly one account is returned, notes pagination has_more is always false, and mentions the authorization object with allowed_tasks. This goes well beyond a generic 'list accounts' description, though it stops short of discussing side-effect-free behavior explicitly.

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 organized into clear sections—purpose, when to use, returns, and example. It is longer than average but every section adds useful context, and the key constraint (one key = one account) is front-loaded at the top.

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, so the description appropriately explains the return shape: account objects with fields plus authorization and pagination behavior. It covers the main workflow and includes a concrete example. Missing details like sandbox semantics and the account filter are covered in the input schema, so the overall picture is largely complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 60%, and the description does not compensate for the undocumented context and pagination input parameters. The example with status adds little beyond the schema's own enum description, and the description never explains the account filter object or what pagination parameters mean for a tool that always returns one account.

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 opens with a specific verb and resource: 'List the accounts this credential can transact on.' It then clarifies the account model—one API key equals one account—so an agent immediately understands exactly what this tool returns and how it differs from other list_* tools.

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 'WHEN TO USE' section explicitly lists clear use cases: discovering account_id before account-scoped calls, checking account status before buying, and introspecting allowed tasks. It does not name alternative tools or state when not to use it, but the context is strong enough for an agent to select it correctly.

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

All Trillboards DOOH Advertising 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