Plendio price comparison

Create a shareable wishlist

create_wishlist

Creates a shareable wishlist ("ønskeseddel") on Plendio from products a person has picked, for example gifts found with a search, once they want a list to send to family or friends. Takes a title (up to 80 characters), a market and 1 to 50 products by Plendio id, each with an optional note of up to 140 characters, and optionally who the list is for (recipient, up to 80 characters) and the day of the occasion (occasion_date, YYYY-MM-DD, today or later). Returns two links, a read-only share link to the list's page on Plendio and a private edit link for changing the list and saving it to a Plendio account, together with the list's items and their best current prices. No login is needed and no personal data is collected. Unknown or unavailable products are reported and not stored. The edit link is a secret: anyone who holds it can change the list. A list that is not viewed or edited for 90 days is deleted. Each request creates a new list.

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": {
      "title": "<title>",
      "items": "<items>"
    },
    "name": "create_wishlist"
  }
}

Input Schema

Name	Required	Description
`items`	Yes	The products on the list: 1 to 50.
`title`	Yes	Name of the list, e.g. "Emmas fødselsdag". Up to 80 characters; markup and links are removed.
`market`	No	Market the list is for: dk, se, de or no. Default: the market of the site you connected to.
`recipient`	No	Optional: who the list is for, e.g. "Emma". Up to 80 characters; markup and links are removed.
`occasion_date`	No	Optional: the day of the occasion as YYYY-MM-DD, today or later (a birthday, Christmas Eve).

Output Schema

Name	Required	Description
`items`	Yes
`notes`	No
`title`	Yes	The list's name, written by whoever made it.
`market`	Yes
`currency`	No	Currency of total_from.
`edit_url`	Yes	Private link for changing the list on Plendio and saving it to an account. Shown once.
`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 were not put on the list, with the reason.
`total_from`	No	Sum of price_from over the available items; absent when their currencies differ or none has a price.
`instruction`	Yes	A line for the user about the two links.
`occasion_date`	No	Day of the occasion, YYYY-MM-DD.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 6, 2026

addedInput schema / properties / occasion_date

Added value: +{
+  "description": "Optional: the day of the occasion as YYYY-MM-DD, today or later (a birthday, Christmas Eve).",
+  "maxLength": 10,
+  "pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}$",
+  "type": "string"
+}

addedInput schema / properties / recipient

Added value: +{
+  "description": "Optional: who the list is for, e.g. \"Emma\". Up to 80 characters; markup and links are removed.",
+  "maxLength": 80,
+  "type": "string"
+}

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

A4.4/5.0

Behavior5/5

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

Goes well beyond the annotations: no login required, no personal data collected, unknown/unavailable products reported but not stored, the edit link is a bearer secret, and idle lists are deleted after 90 days. It also clarifies that it is non-idempotent in effect ('each request creates a new list'), which reinforces idempotentHint=false with concrete meaning.

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?

Purpose and requirements are front-loaded, and most sentences carry real information such as the edit-link secrecy and the 90-day expiry. One dense paragraph repeats several schema-stated limits, which costs a little efficiency.

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?

Even though an output schema exists, the description explains what comes back (share link, private edit link, items with best current prices), plus authentication and retention behavior. For a creation tool with side effects and a secret credential, nothing material is missing.

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 baseline is 3. The description restates the same constraints (title 80 chars, 1–50 products, note 140, occasion_date YYYY-MM-DD today or later) rather than adding new meaning, though it does usefully frame product_id as coming from a search result.

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 and resource ('Creates a shareable wishlist on Plendio') and scopes the source of products ('from products a person has picked'). The closing line 'Each request creates a new list' separates it from add_to_wishlist, which mutates an existing one.

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 a clear condition for use ('once they want a list to send to family or friends') and implicitly routes away from add_to_wishlist by noting every request creates a new list. It never names the sibling explicitly or says when not to use it, so a 4 rather than a 5.

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?