Trillboards DOOH Advertising

by io.github.snehdhruv

Overview Discussions Admin

get_media_buy_delivery

[AdCP Media Buy] Get delivery/performance report for a media buy.

Returns campaign performance with breakdowns by screen, venue, hour, and audience segment.

WHEN TO USE:

Monitoring campaign delivery in real-time
Getting performance breakdowns for optimization
Reporting on campaign results

RETURNS:

delivery: impressions, spend, avg_cpm, unique_screens, fill_rate
breakdowns: by_screen, by_venue, by_hour (top performers)

EXAMPLE: get_media_buy_delivery({ media_buy_id: "mbuy_abc123" })

Input Schema

TableJSON Schema

Name	Required	Description
`dimensions`	No	Reporting dimensions to include. Only "screen" is supported; anything else is returned in dimensions_unsupported rather than silently dropped.
`breakdown_by`	No	Dimensions to break down by (legacy, prefer dimensions). Same single supported value.
`media_buy_id`	Yes	Media buy ID

Schema Changelog

Changes observed during successful MCP inspections.

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"
+}
```

Changed2 schema fields changedAug 17, 2026

changedInput schema / properties / breakdown_by / description

Previous value: -"Dimensions to break down by (legacy, prefer dimensions)"New value: +"Dimensions to break down by (legacy, prefer dimensions). Same single supported value."

changedInput schema / properties / dimensions / description

Previous value: -"Reporting dimensions to include"New value: +"Reporting dimensions to include. Only \"screen\" is supported; anything else is returned in dimensions_unsupported rather than silently dropped."

Changed3 schema fields changedAug 7, 2026
- addedInput schema / properties / breakdown_by / description
```
Added value: +"Dimensions to break down by (legacy, prefer dimensions)"
```
- addedInput schema / properties / dimensions / description
```
Added value: +"Reporting dimensions to include"
```
- addedInput schema / properties / media_buy_id / description
```
Added value: +"Media buy ID"
```
First observedMar 12, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations, the description carries the behavioral burden. It lists return metrics and breakdowns, but it claims breakdowns by venue, hour, and audience segment while the schema says only 'screen' is supported, and it omits the dimensions_unsupported behavior. This is misleading and incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well organized with WHEN TO USE, RETURNS, and EXAMPLE sections and is front-loaded with the main purpose. There is minor redundancy between the opening line and RETURNS, but the structure helps an agent scan it.

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

Completeness2/5

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

No output schema exists, so the description must explain return behavior, which it does only partially. The omission of the single-supported-dimension constraint and the dimensions_unsupported response is a significant gap that could cause an agent to request unsupported breakdowns and misread the results.

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 coverage is 100%, so the schema already documents all parameters clearly, including the critical 'only screen is supported' note. The description's example shows media_buy_id usage and its return summary hints at what dimensions produce, but it does not add meaningful parameter semantics beyond the schema.

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?

States a specific action and resource: 'Get delivery/performance report for a media buy.' The resource (media buy) distinguishes it from many sibling get_* tools, though it does not explicitly name a sibling or alternative.

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?

Provides a WHEN TO USE section with concrete scenarios: real-time monitoring, performance breakdowns for optimization, and reporting. It does not spell out when to prefer a sibling tool like get_campaign_performance or get_analytics, so no explicit exclusion is given.

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?