Plendio price comparison

Add products to a wishlist

add_to_wishlist

Idempotent

Adds products to a wishlist made earlier, given its edit link or the token at the end of it. A product already on the list stays as it is, with its note. A list holds at most 50 products; unknown or unavailable products, and products that no longer fit, are reported and not added. Returns the list's items with their best current prices. The token stops working once the list has been saved to a Plendio account.

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": {
      "edit_token": "<edit_token>",
      "items": "<items>"
    },
    "name": "add_to_wishlist"
  }
}

Input Schema

Name	Required	Description
`items`	Yes	The products to add: 1 to 50. A product already on the list stays as it is, with its note.
`market`	No	Market for the urls in the answer: dk, se, de or no. Default: the market the list was made for.
`edit_token`	Yes	The wishlist's edit link as returned when it was created, or just the token at the end of it.

Output Schema

Name	Required	Description
`added`	No	Product ids put on the list.
`items`	Yes
`notes`	No
`title`	Yes	The list's name, written by whoever made it.
`market`	Yes
`removed`	No	Product ids taken off the list.
`currency`	No	Currency of total_from.
`recipient`	No	Who the list is for, written by whoever made it.
`share_url`	Yes	The list's page on Plendio, read-only.
`item_count`	Yes
`not_stored`	No	Products that could not be added, with the reason.
`total_from`	No	Sum of price_from over the available items; absent when their currencies differ or none has a price.
`not_on_list`	No	Product ids that were not on the list.
`occasion_date`	No	Day of the occasion, YYYY-MM-DD.
`already_on_list`	No	Product ids that were already on the list and were left as they are.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 9, 2026

changedInput schema / properties / items / description

Previous value: -"The products to add: 1 to 50. A product already on the list keeps its place and takes the new note."New value: +"The products to add: 1 to 50. A product already on the list stays as it is, with its note."

changedOutput schema / properties / already_on_list / description

Previous value: -"Product ids that were already on the list (their note was updated)."New value: +"Product ids that were already on the list and were left as they are."

Changed2 schema fields changedNov 6, 2026

addedOutput schema / properties / occasion_date

Added value: +{
+  "description": "Day of the occasion, YYYY-MM-DD.",
+  "type": "string"
+}

addedOutput schema / properties / recipient

Added value: +{
+  "description": "Who the list is for, written by whoever made it.",
+  "type": "string"
+}

AddedOct 1, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Goes well beyond the annotations: a hard 50-product cap, partial-failure semantics (unknown/unavailable/non-fitting products are reported and skipped rather than aborting the call), note preservation for duplicates, and token invalidation after the list is claimed. These are the operational details an agent needs and none are derivable from readOnlyHint/idempotentHint alone; nothing contradicts the annotations.

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?

Four sentences, front-loaded with the action, then limits, then failure behavior, then token lifetime. Dense with no filler, though the return-value clause is somewhat redundant given an output schema exists.

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?

Covers limits, silent-skip behavior, duplicate handling, and token expiry — the things most likely to trip up a caller. The market parameter and the response shape are left entirely to the schema/output schema, which is acceptable given 100% schema coverage and a declared output schema.

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 100%, so the parameters are already fully documented, including the edit_token dual form and the items/note/slug alternatives. The description restates the token forms and duplicate-handling rule but adds no new syntax or format meaning, so the baseline 3 applies.

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 and resource ("Adds products to a wishlist") plus the identifying mechanism (edit link or trailing token). The phrase "made earlier" hints that this is the guest/unclaimed-list counterpart to add_to_my_wishlist, but no sibling is named, so the agent must infer the boundary.

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?

Usage is implied by the requirement for an edit token and by the note that the token stops working once the list is saved to a Plendio account — an agent can reason that this tool is for unclaimed lists. However, it never explicitly states when to prefer this over add_to_my_wishlist or create_wishlist, and there are no stated preconditions for obtaining the token.

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

All Plendio price comparison 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?