Trillboards DOOH Advertising

sync_accounts

[AdCP Accounts] Establish or confirm the account behind this credential.

IMPORTANT — what this does NOT do: it does not provision a new account. This seller's namespace is one account per API key, so a provisioning-mode entry (brand + operator + billing) is LINKED to the account your key already owns and the response says so in warnings[]. Two different brands on one key resolve to the SAME account_id. Register one agent per brand at https://api.trillboards.com/v1/partner/agent/register if you need per-brand separation.

BILLING IS THE ONE SETTING THAT IS APPLIED. Send billing: 'operator' (we invoice you, buying direct) or 'agent' (you are a buying agent consolidating across the brands you front, and we invoice you for all of them — the marketplace-clearing model). The value is stored on the account, reported back by list_accounts, and reflected in action 'updated'. The set we accept is exactly account.supported_billing from get_adcp_capabilities; 'advertiser' is refused, with the reason, because we hold no billing relationship with a third-party advertiser. One key is one account with one invoiced party, so a request declaring two different billing values applies neither and says so.

Everything else is read-only and reports 'unchanged': payment terms, billing entity and notification subscriptions are not per-account state on this platform, and anything sent that was not applied is named in warnings[] rather than silently swallowed.

WHEN TO USE:

The account-setup step at the start of a buying flow
Declaring how you want to be invoiced, before create_media_buy
Confirming your account_id and status before create_media_buy

RETURNS:

accounts: per-entry result with account_id, action ('updated' | 'unchanged' | 'failed'), status, billing, account_scope, and warnings naming anything not applied

EXAMPLE: sync_accounts({ idempotency_key: "8f1c...", accounts: [{ brand: { domain: "acme.example" }, operator: "agency.example", billing: "agent" }] })

Input Schema

TableJSON Schema

Name	Required	Description
`context`	No
`dry_run`	No	Echo what would happen without applying it. Reported back as dry_run.
`accounts`	Yes	Per-account entries. Each uses ONE key shape: `account` (settings-update) or the flat brand + operator + billing trio (provisioning).
`delete_missing`	No	Not supported — this seller never deletes an account from a sync.
`idempotency_key`	Yes	Client-generated key for safe retries. This operation has no side effects, so a replay returns the same result.
`push_notification_config`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 1, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```

Changed3 schema fields changedSep 1, 2026

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."

Changed3 schema fields changedSep 1, 2026

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."

Changed7 schema fields changedAug 7, 2026

addedInput schema / properties / accounts / description

Added value: +"Per-account entries. Each uses ONE key shape: `account` (settings-update) or the flat brand + operator + billing trio (provisioning)."

addedInput schema / properties / accounts / items / properties / billing / description

Added value: +"Who we invoice on this account. APPLIED and stored. 'operator' = you, buying direct; 'agent' = you are a buying agent consolidating across the brands you front. See account.supported_billing in get_adcp_capabilities for the accepted set — 'advertiser' is refused with a reason."

addedInput schema / properties / accounts / items / properties / billing_entity / description
```
Added value: +"Legal/tax details of the invoiced party. Not applied — see warnings."
```
addedInput schema / properties / accounts / items / properties / operator / description
```
Added value: +"Domain of the entity operating on the brand's behalf"
```

addedInput schema / properties / delete_missing / description

Added value: +"Not supported — this seller never deletes an account from a sync."

addedInput schema / properties / dry_run / description

Added value: +"Echo what would happen without applying it. Reported back as dry_run."

addedInput schema / properties / idempotency_key / description

Added value: +"Client-generated key for safe retries. This operation has no side effects, so a replay returns the same result."

AddedJul 28, 2026

TDQS

A5/5.0

Behavior5/5

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

With no annotations provided, the description carries the full behavioral disclosure burden and does so exceptionally. It explicitly states that billing is the only applied setting, everything else reports 'unchanged', unapplied values are named in warnings[], two brands on one key resolve to the same account_id, and 'advertiser' is refused with a reason.

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 long but tightly organized with clear sections: what it does, what it does NOT do, billing behavior, read-only behavior, when to use, returns, and an example. Every sentence earns its place, and the most important caveat is front-loaded immediately after the purpose statement.

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

Completeness5/5

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

This is a complex tool with nested objects, no output schema, and no annotations. The description fully compensates by documenting return fields, giving a concrete example, explaining accepted and refused billing values, and clarifying the one-account-per-key constraint and its consequences for the agent's decisions.

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

Parameters5/5

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

Schema coverage is 67% and the schema already documents several fields, but the description adds substantial meaning beyond it: the two account entry shapes, which settings are persisted vs ignored, how billing values map to invoicing relationships, and how idempotent replays behave. The billing parameter especially gains semantic depth that the enum alone cannot convey.

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 purpose: 'Establish or confirm the account behind this credential.' It then actively distinguishes itself from provisioning by stating it does not create a new account and that per-brand separation is handled by a separate registration endpoint, so an agent can clearly tell this from setup_billing, list_accounts, and register_partner.

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

Usage Guidelines5/5

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

A dedicated 'WHEN TO USE' section lists concrete triggers: account setup, declaring invoicing before create_media_buy, and confirming account_id/status before create_media_buy. It also tells the agent when not to use it, namely when per-brand separation is needed, and points to the registration alternative.

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 tools Inspect

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

Need Help?