Trillboards DOOH Advertising

tasks_list

[AdCP Protocol] List AdCP tasks belonging to your account, newest first.

Returns query_summary (totals and a status breakdown), tasks, and pagination. Filter by status or task type. Scoped to the calling account — an unauthenticated call returns an empty page rather than another account's tasks.

LEGACY NAME. Identical to list_tasks. Prefer list_tasks in new code.

Input Schema

TableJSON Schema

Name	Required	Description
`account`	No
`context`	No
`filters`	No	Narrow the returned tasks.
`pagination`	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 / filters / description
```
Added value: +"Narrow the returned tasks."
```
- addedInput schema / properties / filters / properties / status / description
```
Added value: +"Single task status to match"
```
- addedInput schema / properties / filters / properties / statuses / description
```
Added value: +"Task statuses to match (enums/task-status.json)"
```
- addedInput schema / properties / filters / properties / task_type / description
```
Added value: +"Single task type to match"
```
- addedInput schema / properties / filters / properties / task_types / description
```
Added value: +"Task types to match (enums/task-type.json)"
```
- addedInput schema / properties / pagination / properties / limit / description
```
Added value: +"Page size (max 100, default 50)"
```
- addedInput schema / properties / pagination / properties / offset / description
```
Added value: +"Rows to skip"
```
AddedAug 3, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations, the description carries the disclosure burden and does well: it reveals ordering, return summary components, filtering capability, account scoping, and the unauthenticated edge case. It does not discuss rate limits or explicitly state read-only behavior, but 'list' and the described behavior make the operation 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 compact and front-loaded: core behavior first, return details and scoping second, legacy-alias guidance last. Every sentence adds information and none is wasted.

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?

For a listing tool with no annotations and no output schema, it covers return shape, filtering behavior, ordering, account scoping, the unauthenticated case, and the alias relationship. Nothing essential is missing for an agent to decide whether to call it or the preferred sibling.

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 only 25%, and the description adds account-scoping and filter-dimension semantics, but it does not explain the `account` or `context` objects. The filter and pagination meanings are mostly left to the schema's enum and limit descriptions, so the description only partially compensates for the low coverage.

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 clear verb+resource+scope: 'List AdCP tasks belonging to your account, newest first.' It also explicitly calls out the legacy relationship to `list_tasks`, so an agent understands what this tool is and how it differs from the sibling.

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?

It explicitly names the preferred alternative `list_tasks`, states the two tools are identical, and instructs 'Prefer `list_tasks` in new code.' This is clear when-to-use guidance: use `tasks_list` only for legacy compatibility.

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?