Skip to main content
Glama

Pet Welcome Box – hand-picked gift ideas

Add kit item

add_item

Add an item to an existing pet kit list (requires editToken). Pass the list's marketplace (amazon.com or amazon.se) + locale.

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": {
      "id": "<id>",
      "editToken": "<editToken>"
    },
    "name": "add_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesWishlist / kit list id
urlNo
asinNo
nameNo
emojiNo
titleNo
localeNoUser locale, e.g. en-US (US shoppers → amazon.com) or sv-SE (Sweden → amazon.se). If marketplace and country are omitted, en-US selects amazon.com.
countryNoISO country of the shopper, used when marketplace is omitted: US → amazon.com, SE → amazon.se.
editTokenYesX-Edit-Token from create
marketplaceNoAmazon storefront: amazon.com (United States — 224 hand-picked products, English, USD, /dp/ links tagged sw-petbox-20) or amazon.se (Sweden, default — 440 products, tag sw-petbox-21); ids us / se also work. Optional: when omitted → country, then locale / Accept-Language en-US → amazon.com, otherwise amazon.se. Other storefronts get search links.
searchKeywordsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / country
      Added value: +{
      +  "description": "ISO country of the shopper, used when marketplace is omitted: US → amazon.com, SE → amazon.se.",
      +  "maxLength": 3,
      +  "minLength": 2,
      +  "type": "string"
      +}
    • changedInput schema / properties / locale / description
      Previous value: -"User locale, e.g. en, sv, de, fr, es"New value: +"User locale, e.g. en-US (US shoppers → amazon.com) or sv-SE (Sweden → amazon.se). If marketplace and country are omitted, en-US selects amazon.com."
    • changedInput schema / properties / marketplace / description
      Previous value: -"Amazon storefront domain or id, e.g. amazon.com, amazon.se, us, se. REQUIRED."New value: +"Amazon storefront: amazon.com (United States — 224 hand-picked products, English, USD, /dp/ links tagged sw-petbox-20) or amazon.se (Sweden, default — 440 products, tag sw-petbox-21); ids us / se also work. Optional: when omitted → country, then locale / Accept-Language en-US → amazon.com, otherwise amazon.se. Other storefronts get search links."
    • changedInput schema / required
      Previous value: -[
      -  "id",
      -  "editToken",
      -  "marketplace",
      -  "locale"
      -]New value: +[
      +  "id",
      +  "editToken"
      +]
  2. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations declare this a non-read-only, open-world operation, and the description adds the real constraint the agent needs: an editToken from create is mandatory. It says nothing about duplicate handling, what happens with a stale token, or which of several item-identity fields is actually used.

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?

Two short sentences with the action first and the required token and marketplace/locale constraint immediately after. Nothing is wasted, though 'Pass the list's marketplace' is slightly loose phrasing for what is an optional param.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter mutation with no output schema and only 45% schema coverage, the description should clarify how a product gets identified (asin vs url vs name vs searchKeywords). That core ambiguity is left entirely to the agent, so the definition is thin against the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 45%; id, locale, country, editToken and marketplace are documented in the schema, but url, asin, name, emoji, title and searchKeywords have no description anywhere. The description touches only marketplace and locale and gives no hint about whether url/asin identify a product to resolve or are stored verbatim.

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?

Specific verb plus resource ('Add an item to an existing pet kit list') with the key qualifier that the list must already exist, which separates it from create_wishlist and create_and_fill. It never names those siblings outright, so the differentiation is inferential 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?

'Existing' plus 'requires editToken' implies the create-then-add workflow, and the parenthetical suggests where the token comes from. There is no explicit statement of when not to use this versus create_and_fill, and no mention of prerequisites beyond the token.

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