Skip to main content
Glama

ads_create_sp_keywords

Create SP keywords. L'ad group bersaglio deve essere keyword-targeted: se ha GIÀ product target Amazon rifiuta con otherError (un ad group è keyword O product, mai entrambi) → in quel caso crea un ad group dedicato alle keyword. Ogni keyword: { campaign_id, ad_group_id, keyword_text, match_type (BROAD|PHRASE|EXACT), bid }.

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": {
      "keywords": "<keywords>"
    },
    "name": "ads_create_sp_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYesKeyword da creare: array di { campaignId, adGroupId, keywordText, matchType, bid } (matchType EXACT, PHRASE o BROAD).
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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / keywords / description
      Added value: +"Keyword da creare: array di { campaignId, adGroupId, keywordText, matchType, bid } (matchType EXACT, PHRASE o BROAD)."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing the failure mode: Amazon returns otherError when the ad group already carries product targets, because an ad group is keyword OR product. That is real behavioral context the readOnlyHint/destructiveHint flags do not convey. The write-confirmation flow is left to the schema's confirm_id field.

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

Conciseness3/5

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

The ad-group constraint is front-loaded and valuable, but the trailing field enumeration duplicates the schema, and the mixed Italian/English phrasing makes it harder to scan. Two of the three sentences earn their place.

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

Completeness4/5

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

For a mutating create tool with no output schema, the description covers the key prerequisite, the error condition, and the payload shape, while the schema handles the two-step confirm_id workflow. Nothing an agent needs in order to call it correctly is conspicuously missing.

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 schema already documents all three parameters, and the description largely restates the keyword fields with the same match type values. It also uses snake_case names (campaign_id, ad_group_id) that do not match the schema's camelCase (campaignId, adGroupId), adding mild confusion rather than meaning.

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?

States a specific verb and resource ('Create SP keywords') and immediately scopes it to keyword-targeted ad groups. It is distinguishable from ads_create_sp_negative_keywords and ads_list_sp_keywords by name and content, though it never names a sibling explicitly.

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?

Gives a concrete precondition (the target ad group must be keyword-targeted) and a course of action when it is not (create a dedicated keyword ad group). It stops short of naming the sibling to use for that fallback or ruling out alternatives, so it is strong context rather than full when/when-not guidance.

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