Skip to main content
Glama

ads_create_portfolio

Create an Amazon Ads portfolio to group campaigns (no portfolio-level budget cap; campaigns can then be assigned to it). Same scope as campaigns — no extra authorization needed.

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": {
      "portfolio": "<portfolio>"
    },
    "name": "ads_create_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
portfolioYesPortfolio da creare: oggetto { name, budget? } (formato Amazon Ads).
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. Changed3 schema fields changed
    • addedInput schema / properties / portfolio / description
      Added value: +"Portfolio da creare: oggetto { name, budget? } (formato Amazon Ads)."
    • addedInput schema / properties / portfolio / properties / name / description
      Added value: +"Nome della campagna/portfolio/ad group, visibile in console Amazon Ads."
    • addedInput schema / properties / portfolio / properties / profile_id / description
      Added value: +"Amazon Ads profile id (stringa numerica, da ads_list_profiles). Omesso: profilo predefinito dell'outpost."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, open-world write, so the description's job is to add beyond that; it does contribute auth-relevant context ("same scope as campaigns — no extra authorization needed") and a behavioral constraint (no budget cap). It omits the most consequential behavior for correct invocation: that the call is a two-step preview/confirm flow requiring the same payload plus confirm_id to actually commit.

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

Conciseness4/5

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

A single compact sentence with the core action front-loaded and parenthetical detail that earns its place by preventing a budget-cap misconception. Nothing is wasted, though the trailing authorization clause could be separated for scannability.

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?

Covers purpose, scoping behavior, and auth expectations for a nested-object write against a 100%-documented schema with no output schema, which is close to sufficient. The notable gap is the confirm_id preview-then-commit protocol, which materially changes how an agent must call the tool and is left to the schema alone.

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 coverage is 100%, so all three parameters are already documented and the baseline is 3. The description adds semantic framing of the portfolio object as a campaign grouping, but it also conflicts slightly with the schema, which describes the portfolio as "{ name, budget? }" while the description asserts there is no portfolio-level budget cap — an agent could be unsure whether to pass budget.

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 an Amazon Ads portfolio") and adds what a portfolio is for ("group campaigns"), plus the distinguishing trait that it carries no portfolio-level budget cap, which separates it from campaign-creation siblings. It stops short of naming a sibling such as ads_list_portfolios or ads_create_sp_campaign, so differentiation is inferred rather than explicit.

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

Usage Guidelines3/5

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

Implies the ordering (create the portfolio, then assign campaigns to it), which is genuine when-to-use context. There is no explicit guidance on when not to use it, no mention of checking ads_list_portfolios for an existing portfolio, and no statement of prerequisites beyond the authorization note.

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