Skip to main content
Glama

Trillboards DOOH Advertising

update_media_buy

[AdCP Media Buy] Update an existing media buy (campaign).

Modify budget, targeting, schedule, or status of an existing media buy.

WHEN TO USE:

  • Adjusting campaign budget mid-flight

  • Pausing or resuming a campaign

  • Changing targeting parameters

  • Extending campaign dates

EXAMPLE: update_media_buy({ media_buy_id: "mbuy_abc123", updates: { status: "paused", budget: { daily_usd: 300 } } })

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
extNo
pausedNo
accountNo
contextNo
updatesNoFields to update
canceledNo
end_timeNo
packagesNo
revisionNo
start_timeNo
media_buy_idYesMedia buy ID to update
new_packagesNo
idempotency_keyNo
invoice_recipientNo
reporting_webhookNo
cancellation_reasonNo
push_notification_configNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / additionalProperties
      Previous value: -falseNew value: +true
  2. Changed3 schema fields changed
    • 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."
  3. Changed3 schema fields changed
    • 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."
  4. Changed2 schema fields changed
    • addedInput schema / properties / media_buy_id / description
      Added value: +"Media buy ID to update"
    • addedInput schema / properties / updates / description
      Added value: +"Fields to update"
  5. Changed1 schema field changed
    • addedInput schema / properties / packages / items / properties / creative_assignments
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "creative_id": {
      +        "maxLength": 200,
      +        "minLength": 1,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "creative_id"
      +    ],
      +    "type": "object"
      +  },
      +  "maxItems": 100,
      +  "type": "array"
      +}
  6. Changed1 schema field changed
    • addedInput schema / properties / packages / items / properties / targeting_overlay
      Added value: +{
      +  "anyOf": [
      +    {
      +      "additionalProperties": {},
      +      "type": "object"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  7. Changed14 schema fields changed
    • addedInput schema / properties / account
      Added value: +{
      +  "additionalProperties": {},
      +  "type": "object"
      +}
    • addedInput schema / properties / canceled
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / cancellation_reason
      Added value: +{
      +  "maxLength": 500,
      +  "type": "string"
      +}
    • addedInput schema / properties / end_time
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / ext
      Added value: +{
      +  "additionalProperties": {},
      +  "type": "object"
      +}
    • addedInput schema / properties / idempotency_key
      Added value: +{
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / invoice_recipient
      Added value: +{
      +  "additionalProperties": {},
      +  "type": "object"
      +}
    • addedInput schema / properties / new_packages
      Added value: +{
      +  "items": {
      +    "additionalProperties": {},
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / paused
      Added value: +{
      +  "type": "boolean"
      +}
    • addedInput schema / properties / push_notification_config
      Added value: +{
      +  "additionalProperties": {},
      +  "type": "object"
      +}
    • addedInput schema / properties / reporting_webhook
      Added value: +{
      +  "additionalProperties": {},
      +  "type": "object"
      +}
    • addedInput schema / properties / revision
      Added value: +{
      +  "type": "integer"
      +}
    • addedInput schema / properties / start_time
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "string"
      +    },
      +    {
      +      "const": "asap",
      +      "type": "string"
      +    }
      +  ]
      +}
    • changedInput schema / required
      Previous value: -[
      -  "media_buy_id",
      -  "updates"
      -]New value: +[
      +  "media_buy_id"
      +]
  8. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
      +  "additionalProperties": {},
      +  "type": "object"
      +}
  9. Changed1 schema field changed
    • addedInput schema / properties / packages
      Added value: +{
      +  "items": {
      +    "additionalProperties": true,
      +    "properties": {
      +      "package_id": {
      +        "maxLength": 100,
      +        "minLength": 1,
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "package_id"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
  10. First observed

TDQS

A3.6/5.0
Behavior2/5

Does 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 conveys that this is a mutation tool and lists use cases, but it does not explain merge semantics, whether updates are partial or full replacements, permission requirements, side effects, reversibility, or what the response contains.

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 well-structured with a clear summary, 'WHEN TO USE' bullets, and a concrete example. It is front-loaded, every section earns its place, and the example efficiently demonstrates the expected invocation shape.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex tool with 17 parameters, nested objects, no annotations, and no output schema. The description covers the core update flow well, but it leaves many parameter mechanisms unexplained (e.g., cancellation, idempotency, package changes, webhooks), making it incomplete for full correct invocation in all scenarios.

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 description coverage is only 12%, so the description must compensate. It adds useful semantics by mapping to fields like status, budget, targeting, and dates, and the example clarifies the important `updates` object shape. However, many top-level parameters such as packages, paused, canceled, cancellation_reason, idempotency_key, and webhook settings remain unexplained.

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 states a specific verb and resource: "Update an existing media buy," and further specifies the modifiable dimensions: budget, targeting, schedule, or status. This clearly distinguishes it from creation and read tools such as create_media_buy and get_media_buys by emphasizing 'existing' and 'update.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The 'WHEN TO USE' section provides concrete scenarios: adjusting budget mid-flight, pausing/resuming, changing targeting, and extending dates. It gives clear context for when the tool is appropriate, though it does not explicitly state when not to use it or name alternative tools.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources