[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.
| Name | Required | Description | Default |
|---|---|---|---|
| account | No | ||
| context | No | ||
| filters | No | Narrow the returned tasks. | |
| pagination | No |
Changes observed during successful MCP inspections.
Input schema / additionalPropertiesPrevious value: -falseNew value: +trueInput schema / properties / adcp_major_versionRemoved 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"
-}Input schema / properties / adcp_versionRemoved 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"
-}Input schema / properties / context / descriptionRemoved value: -"Opaque caller-supplied correlation object. Echoed back byte-for-byte, unparsed, on both successful and failed responses; the agent never reads its contents."Input schema / properties / adcp_major_versionAdded 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"
+}Input schema / properties / adcp_versionAdded 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"
+}Input schema / properties / context / descriptionAdded value: +"Opaque caller-supplied correlation object. Echoed back byte-for-byte, unparsed, on both successful and failed responses; the agent never reads its contents."Input schema / properties / filters / descriptionAdded value: +"Narrow the returned tasks."Input schema / properties / filters / properties / status / descriptionAdded value: +"Single task status to match"Input schema / properties / filters / properties / statuses / descriptionAdded value: +"Task statuses to match (enums/task-status.json)"Input schema / properties / filters / properties / task_type / descriptionAdded value: +"Single task type to match"Input schema / properties / filters / properties / task_types / descriptionAdded value: +"Task types to match (enums/task-type.json)"Input schema / properties / pagination / properties / limit / descriptionAdded value: +"Page size (max 100, default 50)"Input schema / properties / pagination / properties / offset / descriptionAdded value: +"Rows to skip"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses several behavioral traits: newest-first ordering, account scoping, and that unauthenticated calls return an empty page rather than another account's data. It also names the returned top-level components. This is solid for a read/list operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is tight and front-loaded: the purpose appears in the first sentence, followed by return value names, filtering capability, and a key scoping caveat. Every sentence contributes useful information without redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool has nested parameters, no output schema, and no annotations, so the description must carry more weight. It provides a helpful overview of return values, filtering, and scope, but it does not explain pagination usage, the meaning of the account/context objects, or task payload structure. Gaps remain for an agent to invoke it optimally.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 25%, so the description must compensate, but it only mentions 'filter by status or task type.' It adds no meaning for the account, context, or pagination parameters beyond what the schema already shows. This is insufficient given the low coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'List AdCP tasks belonging to your account, newest first.' It is clear about what the tool does and even adds an ordering guarantee. It does not explicitly distinguish itself from sibling tools such as tasks_list or tasks_get, so it misses the top score.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides context about filtering and account scoping, but gives no explicit guidance on when to use this tool versus alternatives like tasks_list, tasks_get, or get_task_status. No exclusions or selection criteria are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.