Skip to main content
Glama

Nova Amazon MCP Server

list_events

Read-only

The seller's EVENTS — the dated notes Nova draws on the charts to explain a movement: a price change, a content change (title, bullets, images, A+), a PPC change, a product launch, anything else the seller did. Read them when explaining a movement (what changed around that date?) and before create_event (is it already logged?). Filters: a date window, accounts, marketplaces, ASINs (child or parent, no need to know which), types, a text search. Newest first, 20 per page by default.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLatest event date, inclusive (YYYY-MM-DD).
fromNoEarliest event date, inclusive (YYYY-MM-DD).
asinsNoEvents about any of these ASINs, child or parent.
limitNoPage size (default 20).
typesNoEvent types to keep. Omit for every type.
offsetNo
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.
searchNoWords to find in the description or the type.
accountsNoRestrict to a subset of your own seller account IDs (from list_accounts). Omit to include all your accounts. A brand/account name is accepted and resolved to its id when it matches one of your accounts unambiguously; a label that carries the id ("Brand (A1B2C3D4E5F6G)") resolves to that id.
marketplacesNoCountry codes (ES, FR), domains (amazon.es) or marketplace ids. Omit for every marketplace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds behavior the annotations do not carry — newest-first ordering and a default page size of 20. The ASIN parent/child resolution note ('no need to know which') is a useful operational detail, though nothing is said about what a returned event record contains.

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?

Content is front-loaded and dense: what events are, when to read them, then the filter inventory. A few phrases ('anything else the seller did') are explanatory flavor rather than operational detail, but overall the length is justified for a 10-parameter tool.

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, all-optional read tool with no output schema, the definition supplies purpose, usage triggers, ordering and page-size defaults. It stops short of describing the shape of a returned event or how to page past the first 20, which would be the remaining gap.

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 90%, so the schema already documents every filter, including the default of 20 and the child/parent ASIN behavior. The description's filter list largely restates the schema; its only marginal additions are the '20 per page' framing and the 'no need to know which' reassurance, and offset is left unmentioned.

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?

The description gives a specific verb and resource ("The seller's EVENTS") and then defines the resource concretely as dated notes covering price/content/PPC changes, launches and 'other' — matching the type enum. This makes it immediately distinguishable from sibling query_* tools and from create_events.

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?

It names two concrete triggers: read them when explaining a movement (what changed around that date?) and before create_event to check whether it is already logged. That is explicit when-to-use plus a named sibling alternative, leaving nothing to inference.

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.