dv360.line_items.listRetrieve line items for a specified DV360 advertiser by advertiser_id, enabling agents to inspect campaign structure and manage ad inventory.
List line items 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 burden of behavioral disclosure. It says this is a list operation, but does not mention read-only behavior, pagination, rate limits, or any authentication/scope requirements.
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 a single front-loaded sentence with no filler. Every word contributes to identifying the operation and its scope.
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?
For a one-parameter list tool with an output schema, the description covers the core operation and the meaning of the advertiser scope. However, with no annotations and no schema descriptions, it leaves gaps around pagination behavior and usage distinctions from sibling list tools.
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 0%, so the description must compensate for the single advertiser_id parameter. 'Under a DV360 advertiser' clarifies that advertiser_id identifies the parent advertiser whose line items are returned, but gives no format or example.
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 line items, scoped to a DV360 advertiser. It inherently distinguishes this read operation from sibling mutations like dv360.line_item.update and dv360.line_item.set_status, but does not explicitly route against other list siblings.
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 phrase 'under a DV360 advertiser' implies the required advertiser context, but there is no explicit guidance on when to use this tool versus related listing tools such as dv360.campaigns.list or dv360.insertion_orders.list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.