create_wishlistCreate a teacher gift wishlist. Returns id, editToken, ownerUrl, shopUrl, wishlist, storage. Save editToken for add_wishlist_item. OpenAPI: createWishlist.
| Name | Required | Description | Default |
|---|---|---|---|
| items | No | ||
| locale | No | User locale, e.g. en, sv, de, fr, es | |
| subject | No | ||
| occasion | No | ||
| budgetBand | No | ||
| marketplace | No | Amazon storefront domain or id for the end user, e.g. amazon.se, amazon.com, se, de. REQUIRED. | |
| teacherName | No | ||
| giftCategories | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already mark this as a non-read-only, open-world operation. The description adds useful behavioral context by listing key return fields and specifically noting that editToken must be saved for add_wishlist_item.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short and front-loaded with purpose, followed by return fields and the next-step token usage. The OpenAPI reference is minor but does not significantly detract.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
It partially compensates for the absent output schema by naming return fields, but with 8 parameters and only 25% schema coverage, the lack of parameter explanation leaves the definition incomplete for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is only 25%, with 8 parameters, yet the description does not explain any parameter semantics. It adds no meaning for items, subject, occasion, budgetBand, teacherName, giftCategories, or the required marketplace field.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a clear verb and resource: 'Create a teacher gift wishlist.' It is distinguishable from most siblings, though it does not explicitly clarify how it differs from create_and_fill.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It implies a workflow by saying 'Save editToken for add_wishlist_item,' but does not state when to use this tool instead of alternatives like create_and_fill, nor does it describe prerequisites or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.