Trillboards DOOH Advertising

activate_signal

[AdCP Signals] Activate an audience signal for DSP targeting.

Returns an activation_key token for referencing this signal activation. Free-form Trillboards signal labels remain custom parameters. IAB Audience Taxonomy 1.1 segments are emitted only when registered IDs are supplied explicitly.

WHEN TO USE:

Converting audience signals into actionable targeting parameters
Activating already-curated, registered IAB segment IDs for programmatic requests
Creating reusable targeting configurations

RETURNS:

activation_key: Token for referencing this activation (24h expiry)
targeting: { iab_segments, iab_taxonomy_version, custom_params }
screen_count, provider, data_source, methodology

EXAMPLE: User: "Activate the registered $100k-$149k household-income segment on my screens" activate_signal({ signal_type: "audience", parameters: { iab_audience_segment_ids: ["68"] }, screen_ids: ["507f1f77bcf86cd799439011"] })

Input Schema

TableJSON Schema

Name	Required	Description
`parameters`	Yes	Signal parameters to activate as targeting
`screen_ids`	No	Specific screens to activate on (optional, defaults to all partner screens)
`signal_type`	Yes	Type of signal to activate (e.g., "audience", "venue", "behavior")
`destinations`	No	Where to push activated segments
`signal_agent_segment_id`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 1, 2026
- addedInput schema / properties / signal_agent_segment_id
```
Added value: +{
+  "maxLength": 120,
+  "type": "string"
+}
```
Changed2 schema fields changedSep 1, 2026
- changedInput schema / additionalProperties
```
Previous value: -falseNew value: +true
```
- removedInput schema / properties / context
```
Removed value: -{
-  "additionalProperties": {},
-  "type": "object"
-}
```

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

Changed1 schema field changedSep 1, 2026
- addedInput schema / properties / context
```
Added value: +{
+  "additionalProperties": {},
+  "type": "object"
+}
```
Changed6 schema fields changedAug 7, 2026
- addedInput schema / properties / destinations / description
```
Added value: +"Where to push activated segments"
```
- addedInput schema / properties / parameters / description
```
Added value: +"Signal parameters to activate as targeting"
```
- addedInput schema / properties / parameters / properties / iab_audience_segment_ids / description
```
Added value: +"Explicit registered IAB Audience Taxonomy 1.1 IDs; inferred labels are never auto-mapped"
```
- addedInput schema / properties / parameters / properties / lifestyle / description
```
Added value: +"Lifestyle segment key"
```
- addedInput schema / properties / screen_ids / description
```
Added value: +"Specific screens to activate on (optional, defaults to all partner screens)"
```
- addedInput schema / properties / signal_type / description
```
Added value: +"Type of signal to activate (e.g., \"audience\", \"venue\", \"behavior\")"
```

Changed1 schema field changedJul 21, 2026

addedInput schema / properties / parameters / properties / iab_audience_segment_ids

Added value: +{
+  "items": {
+    "pattern": "^(?:iab:)?[1-9]\\d*$",
+    "type": "string"
+  },
+  "maxItems": 50,
+  "type": "array"
+}

First observedMar 12, 2026

TDQS

A4.4/5.0

Behavior4/5

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

With no annotations, the description carries behavioral weight and reveals non-obvious behavior: activation keys expire in 24 hours, IAB segments are emitted only when registered IDs are supplied explicitly, and free-form labels remain custom parameters. It also lists return fields. It does not disclose idempotence, overwrite semantics, or permission requirements, but it provides substantial behavior beyond the schema.

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 front-loaded purpose, WHEN TO USE, RETURNS, and EXAMPLE sections with no filler. Every section carries operational information, and the structure lets an agent scan it quickly.

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?

Given no output schema and no annotations, the RETURNS list and example materially help the agent understand the call's outcome and shape. The main gaps are that signal_type's other values (venue, behavior) and the destinations parameter are not addressed, so less canonical calls would rely on schema-only inference.

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

Parameters4/5

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

Schema coverage is 80%, so the baseline is 3. The description adds a concrete example mapping a natural-language income segment to iab_audience_segment_ids: ['68'], plus the rule that inferred labels are never auto-mapped. It also clarifies the role of screen_ids through the example, though destinations and other signal_type values are not discussed.

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 'Activate an audience signal for DSP targeting,' identifying a specific verb, resource, and use context. It further differentiates from siblings like get_signals and semantic_audience_search by stating it returns an activation_key token for referencing the activation.

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?

A dedicated WHEN TO USE section lists three concrete invocation contexts, including converting audience signals into targeting parameters and activating registered IAB segment IDs. It does not mention when not to use this tool or name alternative sibling tools, so it stops short of the strongest exclusion guidance.

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?