dv360.insertion_orders.listLists insertion orders under a specified DV360 advertiser so you can review campaign structure and manage orders by advertiser ID.
List insertion orders under a DV360 advertiser.
| Name | Required | Description | Default |
|---|---|---|---|
| advertiser_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.5.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, yet it discloses nothing about pagination, page size, result caps, ordering, or permission requirements. Only the implicit read-only nature of 'List' hints at behavior.
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?
One front-loaded sentence with no filler. It is appropriately terse for a simple listing tool, though the brevity comes at the cost of the missing detail noted elsewhere rather than being efficiently informative.
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?
An output schema exists, so return values need not be explained, but for a paginated list endpoint on a large ad platform the description omits paging, limits, and result-set behavior. Combined with a 0%-documented parameter and no annotations, an agent is left guessing at invocation details.
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 coverage is 0% and the single parameter has no description, so the description must compensate. 'Under a DV360 advertiser' confirms that advertiser_id selects the parent advertiser, but it says nothing about ID format (numeric string vs. 'customers/123' style) or whether child filters exist.
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?
States a specific verb and resource ('List insertion orders') and scopes it to 'under a DV360 advertiser'. The resource is distinct from siblings like dv360.campaigns.list and dv360.line_items.list, so an agent can select it without opening the schema, though no sibling is named explicitly.
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?
There is no guidance on when to use this versus other DV360 listing tools, no prerequisites (advertiser must exist, auth scope), and no note on filtering or paging behavior. The listing intent is only implied by the verb.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.