Skip to main content
Glama
Sign In
OrbiAds

OrbiAds

Official
by OrbiAds
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

line_item_lifecycle

Manage Google Ad Manager line item status: activate, pause, archive, or resume delivery. Archive requires confirmation token and cannot be undone.

Instructions

Perform lifecycle status transitions on a GAM Line Item (activate, pause, archive, resume).

MODE: write AUTH: OAuth 2.0 required CREDITS: 0.5 credits. Confirmation token required for archive. OUTPUT: Returns {line_item_id, previous_status, new_status} WHEN TO USE: Use this for status transitions only. For data updates (targeting, budget, dates), use the line_items update action. DESTRUCTIVE: archive cannot be undone from the API.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "line_item_id": "<line_item_id>",
      "lifecycle_action": "<lifecycle_action>",
      "network_code": "<network_code>"
    },
    "name": "line_item_lifecycle"
  }
}

Input Schema

NameRequiredDescriptionDefault
line_item_idYesGAM Line Item ID.
network_codeYesGAM network code.
lifecycle_actionYesactivate: start delivery. pause: stop delivery temporarily. resume: restart a paused line item. archive: permanently remove from serving (destructive).
confirmation_tokenNoRequired for lifecycle_action=archive. Obtain from a prior estimate_cost call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • changedInput schema / properties / confirmation_token / description
      Previous value: -"Write-confirmation token (required for destructive transitions)."New value: +"Required for lifecycle_action=archive. Obtain from a prior estimate_cost call."
    • changedInput schema / properties / lifecycle_action / description
      Previous value: -"Lifecycle transition to apply."New value: +"activate: start delivery. pause: stop delivery temporarily. resume: restart a paused line item. archive: permanently remove from serving (destructive)."
  2. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

No annotations provided, so description carries full burden. Discloses destructive nature of archive, OAuth 2.0 requirement, 0.5 credits, output structure, and confirmation token necessity.

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?

Very concise, each sentence adds value. Front-loaded with key info, uses bullet points for clarity, and avoids unnecessary words.

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?

No output schema, but description includes output structure. Covers auth, credits, destructive action, and prerequisite for archive. Complete for a lifecycle tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema has 100% coverage with clear descriptions. Description adds context like confirmation token from estimate_cost call, but schema already provides good understanding.

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?

Clearly states it performs lifecycle status transitions (activate, pause, archive, resume) on a GAM Line Item. Distinguishes from sibling tool 'line_items' which is for data updates.

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?

Explicitly says when to use: only for status transitions. For data updates, use line_items update action. Also mentions confirmation token requirement for archive.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools