Sellantica Amazon Ads

List customer search terms

get_search_terms

Read-only

List customer search terms that triggered ads for an Amazon Ads profile, aggregated per (search term, campaign, ad group) over a date range, sorted by clicks descending. Metrics default to the 14-day attribution window and the marketplace-local last 30 days ending yesterday -- the same totals the Sellantica master table shows; use attribution_window to select 1d, 7d, 14d, or 30d instead. Useful for harvesting new keywords or finding negation candidates. profile_id must come from list_profiles.

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": {
      "profile_id": "<profile_id>"
    },
    "name": "get_search_terms"
  }
}

Input Schema

Name	Required	Description	Default
`end`	No	YYYY-MM-DD, default yesterday in the marketplace's local calendar
`limit`	No
`start`	No	YYYY-MM-DD, default 30 days before today in the marketplace's local calendar
`offset`	No
`min_clicks`	No	Only include search terms with at least this many clicks in the window
`min_orders`	No	Only include search terms with at least this many orders in the window
`profile_id`	Yes	Amazon Ads profile id (from list_profiles)
`profile_pk`	No	Optional Sellantica profile primary key to disambiguate duplicate profile_id rows (from list_profiles)
`campaign_id`	No	Amazon campaign id (from get_campaigns)
`attribution_window`	No	Attribution window for sales, orders and ACoS: purchases within N days after the ad click. Default 14d matches the Sellantica dashboard and master table. Amazon's console shows 7d for sellers and 14d for vendors.	14d

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 6, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real context beyond that: the default metrics window (marketplace-local last 30 days ending yesterday), the 14-day attribution default and its equivalence to the Sellantica master table. It does not discuss row limits or pagination behavior, which is the remaining gap.

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?

Purpose and grain are front-loaded in the first sentence; defaults, use cases, and the prerequisite follow in a logical order. Every sentence carries information an agent needs and there is no filler.

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 10-parameter read tool with no output schema, the description covers grain, sorting, temporal defaults, and attribution semantics well. It never mentions pagination (limit/offset exist in the schema but their behavior on result ordering is undocumented) or what columns come back, leaving a modest gap.

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 80%, so the baseline is 3. The description goes beyond it by explaining what attribution_window means semantically (purchases within N days after click, 7d for sellers/14d for vendors) and by reinforcing the date defaults, adding genuine meaning the schema does not.

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 plus the exact aggregation grain '(search term, campaign, ad group)' and sort order '(clicks descending)'. An agent can distinguish this from get_targets or get_harvesting_candidates without opening the schema.

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?

Names concrete use cases ('harvesting new keywords or finding negation candidates') and routes the agent to list_profiles for the required profile_id. It stops short of naming the sibling tools that overlap (get_harvesting_candidates, get_negative_targets) or stating when not to use it, so it is clear but not fully exclusionary.

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

All Sellantica Amazon Ads tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?