Trillboards DOOH Advertising

get_signals

[AdCP Signals] Get real-time audience signals from DOOH screens.

This is an AdCP (Ad Context Protocol) compliant tool. It returns deterministic audience signals captured by edge AI (vision + audio + speech) on available screens.

WHEN TO USE:

Discovering available audience signals before buying inventory
Evaluating audience composition at specific venues or locations
Building targeting segments based on real-time audience data

Unlike probabilistic data, these signals are DETERMINISTIC — captured by on-device cameras and microphones, analyzed by ML Kit and Gemini Vision.

RETURNS:

signals: Array of per-screen signal objects with demographics, venue, behavior, geo
metadata: total_screens, matching_screens, screens_with_live_data

EXAMPLE (AdCP form — natural language): User: "What audience signals are available at retail locations?" get_signals({ signal_spec: "shoppers in retail venues, demographics and behavior" })

EXAMPLE (structured form): get_signals({ signal_spec: { signal_types: ["demographics", "behavior"], filters: { venue_type: "retail" } } })

Input Schema

TableJSON Schema

Name	Required	Description	Default
`pagination`	No
`signal_spec`	No	Natural language description of the desired signals (AdCP form), or a structured Trillboards signal specification.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 1, 2026

addedInput schema / properties / pagination

Added value: +{
+  "additionalProperties": false,
+  "properties": {
+    "cursor": {
+      "maxLength": 200,
+      "type": "string"
+    },
+    "max_results": {
+      "maximum": 100,
+      "minimum": 1,
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

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

Changed6 schema fields changedSep 1, 2026

addedInput schema / properties / context

Added value: +{
+  "additionalProperties": {},
+  "type": "object"
+}

removedInput schema / properties / signal_spec / additionalProperties
```
Removed value: -false
```

addedInput schema / properties / signal_spec / anyOf

Added value: +[
+  {
+    "maxLength": 2000,
+    "type": "string"
+  },
+  {
+    "additionalProperties": false,
+    "properties": {
+      "filters": {
+        "additionalProperties": false,
+        "properties": {
+          "city": {
+            "maxLength": 100,
+            "type": "string"
+          },
+          "income": {
+            "type": "string"
+          },
+          "lifestyle": {
+            "type": "string"
+          },
+          "state": {
+            "maxLength": 100,
+            "type": "string"
+          },
+          "venue_type": {
+            "maxLength": 50,
+            "type": "string"
+          }
+        },
+        "type": "object"
+      },
+      "signal_types": {
+        "items": {
+          "enum": [
+            "demographics",
+            "venue",
+            "geo",
+            "behavior"
+          ],
+          "type": "string"
+        },
+        "type": "array"
+      }
+    },
+    "type": "object"
+  }
+]

changedInput schema / properties / signal_spec / description

Previous value: -"AdCP signal specification"New value: +"Natural language description of the desired signals (AdCP form), or a structured Trillboards signal specification."

removedInput schema / properties / signal_spec / properties

Removed value: -{
-  "filters": {
-    "additionalProperties": false,
-    "description": "Filter criteria for signal query",
-    "properties": {
-      "city": {
-        "description": "Filter by city",
-        "maxLength": 100,
-        "type": "string"
-      },
-      "income": {
-        "description": "Filter by income level",
-        "type": "string"
-      },
-      "lifestyle": {
-        "description": "Filter by lifestyle segment",
-        "type": "string"
-      },
-      "state": {
-        "description": "Filter by state",
-        "maxLength": 100,
-        "type": "string"
-      },
-      "venue_type": {
-        "description": "Filter by venue type",
-        "maxLength": 50,
-        "type": "string"
-      }
-    },
-    "type": "object"
-  },
-  "signal_types": {
-    "description": "Types of signals to retrieve",
-    "items": {
-      "enum": [
-        "demographics",
-        "venue",
-        "geo",
-        "behavior"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  }
-}

removedInput schema / properties / signal_spec / type
```
Removed value: -"object"
```

Changed8 schema fields changedAug 7, 2026
- addedInput schema / properties / signal_spec / description
```
Added value: +"AdCP signal specification"
```
- addedInput schema / properties / signal_spec / properties / filters / description
```
Added value: +"Filter criteria for signal query"
```
- addedInput schema / properties / signal_spec / properties / filters / properties / city / description
```
Added value: +"Filter by city"
```
- addedInput schema / properties / signal_spec / properties / filters / properties / income / description
```
Added value: +"Filter by income level"
```
- addedInput schema / properties / signal_spec / properties / filters / properties / lifestyle / description
```
Added value: +"Filter by lifestyle segment"
```
- addedInput schema / properties / signal_spec / properties / filters / properties / state / description
```
Added value: +"Filter by state"
```
- addedInput schema / properties / signal_spec / properties / filters / properties / venue_type / description
```
Added value: +"Filter by venue type"
```
- addedInput schema / properties / signal_spec / properties / signal_types / description
```
Added value: +"Types of signals to retrieve"
```
First observedMar 12, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses that signals are deterministic, real-time, captured by on-device cameras/microphones, and analyzed via ML Kit and Gemini Vision. It also states what the tool returns. It does not explicitly state that this is a read-only operation, but the verb 'get' and the return-focused description make the read-only nature clear.

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 well-structured with clear sections: a one-line summary, context, WHEN TO USE, returns, and examples. It is longer than average but every section adds useful information, and the critical summary is front-loaded. The two example forms are especially valuable and not redundant.

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?

Given there is no output schema, the description compensates by enumerating the return shape: signals array with demographics, venue, behavior, geo, plus metadata with screen counts. The optional and nested signal_spec is fully explained with examples, and pagination is the only uncovered parameter, which is minor. For a read-oriented signal query tool, this is complete enough for an agent to call it correctly.

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 description coverage is only 50%, so the description must compensate, especially for signal_spec. It does so thoroughly by explaining both the AdCP natural-language form and the structured form, and by providing two concrete examples. The pagination parameter is not mentioned, but its schema is self-explanatory and the description's focus on signal_spec is where the real ambiguity lies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a clear verb-resource pair: 'Get real-time audience signals from DOOH screens,' and elaborates that signals are deterministic audience data captured by edge AI. It does not explicitly differentiate from sibling tools like get_live_audience or get_attention_metrics, but the AdCP framing and deterministic-data emphasis give it a distinct identity.

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 lists three concrete business scenarios: discovering signals before buying, evaluating venue audience composition, and building targeting segments. It also contrasts against probabilistic data, which helps an agent choose this over probabilistic alternatives. It does not name specific sibling tools or exclusion conditions, so it stops short of full routing 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?