Skip to main content
Glama

Nova Amazon MCP Server

set_tacos_default_target

Destructive

Set the organization's DEFAULT TACOS target: the target every product without its own is held against (12 % until the organization sets one). A WHOLE percent from 0 to 100 (12 = 12 %, never 0.12; 0 = no ads wanted by default). Changing it touches no product's own target (import_tacos_targets sets those, and a null target there sends a product back to this default). TWO-STEP: call WITHOUT commit to preview current → new, show the user, then commit with the confirmationToken. A committed change is announced to the Nova team, with your reason: say why. One workspace in scope = implicit; several = pass workspace. Requires the OAuth connection and the OWNER role.

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": {
      "target": "<target>"
    },
    "name": "set_tacos_default_target"
  }
}

Input Schema

NameRequiredDescriptionDefault
commitNoOmit/false = preview (no write). true = write; requires the confirmationToken from the preview.
reasonNoOne sentence, ALWAYS IN ENGLISH (regardless of the conversation language), on WHY you are making this call — the user question or your analytical goal. Recorded so the seller can see how their data is used.
targetYesThe default TACOS target, a whole percent from 0 to 100 (12 = 12 %).
workspaceNoWorkspace id or name. Required only when several workspaces are in scope.
confirmationTokenNoThe token the preview returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare a non-read-only, destructive write, and the description adds material context beyond them: the 12% built-in fallback, that 0 means no ads wanted, that no product's own target is touched, the two-step preview/commit gate, that committed changes are announced to the Nova team with the supplied reason, and that OAuth plus the OWNER role are required. The only gap is that reversal/undo of a committed change is not addressed, which matters for a destructive write.

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?

Front-loads what the target is, then the value rule, then the two-step protocol and prerequisites; every clause carries information and there is no filler. It is dense to the point of being a single run-on paragraph, which slightly hurts scanability for a five-parameter tool.

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?

For a destructive write with no output schema, it covers defaults, value semantics, the preview/commit protocol, side effects (team announcement), permissions, and workspace scoping. An agent has everything needed to invoke it correctly on the first try.

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?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning: target must be a whole percent (12, never 0.12) with 0 having a specific semantic, workspace is only needed when several are in scope, and the confirmationToken must come from the preview. It largely duplicates the schema's percent explanation, which keeps it from a 5.

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?

States a specific verb and resource ('Set the organization's DEFAULT TACOS target') and defines it inline: 'the target every product without its own is held against'. It also distinguishes itself from the sibling import_tacos_targets, which sets per-product targets, so an agent can tell the two apart without opening either schema.

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?

Explicit when-to-use sequencing: call without commit to preview, show the user, then commit with the confirmationToken. It also names the alternative (import_tacos_targets) and its interaction with this default, plus the workspace rule (implicit with one workspace, pass `workspace` with several).

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.