Skip to main content
Glama

ads_update_sp_ad_group

Destructive

Update a SP ad group

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": {
      "ad_group_id": "<ad_group_id>",
      "patches": "<patches>"
    },
    "name": "ads_update_sp_ad_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
patchesYesCampi da modificare (solo quelli indicati): es. state, daily_budget, dynamic_bidding.
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
confirm_idNoToken di conferma ritornato dall'anteprima. Ripassa lo STESSO payload + confirm_id per eseguire davvero la scrittura.
ad_group_idYesId ad group Amazon Ads (stringa numerica, da ads_list_*_ad_groups).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / ad_group_id / description
      Added value: +"Id ad group Amazon Ads (stringa numerica, da ads_list_*_ad_groups)."
    • addedInput schema / properties / patches / description
      Added value: +"Campi da modificare (solo quelli indicati): es. state, daily_budget, dynamic_bidding."
  2. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already flag destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is partly covered. However, the description says nothing about the notable behavior encoded in the schema: writes require a preview then a re-submission with the same payload plus confirm_id. For a destructive mutation, that two-step confirmation flow is exactly the kind of context the description should surface.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

At five words it is short but under-specified rather than concise; there is no structure or front-loaded detail because there is essentially no content. The single phrase merely restates the tool name and title.

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?

For a destructive, open-world mutation with a nested patches object and an unresolved confirm_id workflow, the description omits what can be changed, whether the operation is atomic, and how confirmation works. Annotations and the rich schema carry most of the burden, but the definition is not complete enough on its own.

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 100%, so the parameters (patches, account_id, confirm_id, ad_group_id) are already documented in the schema, and the baseline is 3. The description adds no meaning beyond the schema, so it neither compensates nor detracts.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Update a SP ad group" gives a specific verb (update) and resource (SP ad group), and the "SP" token distinguishes it from the sibling ads_update_sb_ad_group / ads_update_sd_ad_group. It stops short of saying which aspects of the ad group are mutable, but the resource and scope are unambiguous.

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

Usage Guidelines2/5

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

The description offers no when-to-use guidance, no prerequisites, and no routing to alternatives such as ads_create_sp_ad_group or the campaign/keyword-level update siblings. The only usage information lives in the schema (confirm_id preview flow), not the description.

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