Skip to main content
Glama

get_aplus_document

Read-only

READ-ONLY. Dettaglio di UN documento A+ (stato, badge, ASIN associati, tipi di modulo). content_reference_key si prende da list_aplus_documents o audit_aplus_coverage. include_content=true restituisce anche i moduli completi. NB: i moduli A+ sono TIPIZZATI (STANDARD_TEXT, STANDARD_COMPARISON_TABLE, …), non HTML libero — un "HTML pronto" generato altrove va rimappato su questi tipi, non incollato.

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": {
      "content_reference_key": "<content_reference_key>"
    },
    "name": "get_aplus_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
account_idNoID dell'outpost Amazon (= un seller su uno specifico marketplace; vedi list_clients). Opzionale se il token è legato a un solo outpost.
include_contentNotrue = includi i moduli completi
content_reference_keyYesChiave di riferimento del documento A+ (da list_aplus_documents).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / content_reference_key / description
      Added value: +"Chiave di riferimento del documento A+ (da list_aplus_documents)."
  2. First observed

TDQS

A4.2/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 the leading "READ-ONLY" is largely redundant. What the description does add beyond annotations is genuinely useful: the size/branching effect of include_content, and the warning that A+ modules are typed structures (STANDARD_TEXT, STANDARD_COMPARISON_TABLE, …) rather than free HTML, so externally generated HTML must be remapped rather than pasted. That is a real behavioral constraint not present in any structured field. No mention of error modes or missing-document behavior keeps it at 4.

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-loaded with the scope statement, then the key source, then the option flag, then the typing caveat — a logical order with no filler sentences. The opening "READ-ONLY" duplicates the annotation and is the one removable element; the NB caveat is long but earns its place because it prevents a real misuse.

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?

There is no output schema, and the description compensates by naming the returned fields (status, badge, ASINs, module types) and the effect of include_content. Combined with the documented parameter sources and the module-typing caveat, an agent has everything needed to call this correctly and interpret the result.

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 all three parameters are already documented in the input schema, which sets the baseline at 3. The description adds only marginal meaning: it names audit_aplus_coverage as an additional source for content_reference_key (the schema names only list_aplus_documents) and restates that include_content=true yields full modules. account_id is not discussed at all in the description.

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+resource ("Dettaglio di UN documento A+") and immediately enumerates what comes back: stato, badge, ASIN associati, tipi di modulo. The emphasis on "UN" singles-document scope cleanly separates it from the list sibling, and the name of the companion list tool reinforces the distinction.

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 the key prerequisite explicitly: content_reference_key comes from list_aplus_documents or audit_aplus_coverage, which tells the agent how to obtain the required argument. It also states the include_content=true branch. It stops short of stating when NOT to call it (e.g., for coverage overview use audit_aplus_coverage instead), so it is strong but not a full when/when-not/alternatives matrix.

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