Plendio price comparison

Rename or update my list

update_my_wishlist

DestructiveIdempotent

Changes a list the signed-in shopper owns, by list_id: its title, who it is for (recipient) and the event date (YYYY-MM-DD). Only the fields given are changed; an empty recipient or event_date clears it. Requires sign-in.

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": {
      "list_id": "<list_id>"
    },
    "name": "update_my_wishlist"
  }
}

Input Schema

Name	Required	Description
`title`	No	New title, up to 80 characters; markup and links are removed.
`market`	No	Market for the links and prices in the answer: dk, se, de or no.
`list_id`	Yes	The list's id (list_id).
`recipient`	No	Who the list is for, e.g. a first name; up to 80 characters. Empty clears it.
`event_date`	No	The day the gifts are for, YYYY-MM-DD. Empty clears it.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Beyond the annotations (destructiveHint=true, idempotentHint=true, openWorldHint=true), the description discloses the partial-update contract ('Only the fields given are changed') and the clearing semantics for empty recipient/event_date, plus the auth requirement. That is the kind of context an agent needs and cannot get from the hints alone.

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?

Three tight sentences, front-loaded with the verb, resource and keying parameter. The parenthetical 'YYYY-MM-DD' slightly duplicates the schema's event_date description but costs almost nothing.

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?

For a destructive mutation with five params and no output schema, the definition covers keying, partial-update behavior, clearing rules and auth. The only real gap is that the market parameter's role in the response is never mentioned.

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 the baseline is 3 and the schema already documents types, max lengths and clearing behavior. The description paraphrases title, recipient and event_date but adds nothing new, and it omits the market parameter entirely, so no credit above baseline.

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?

States a specific verb and resource ('Changes a list the signed-in shopper owns, by list_id') and enumerates the mutable fields. The ownership qualifier implicitly separates it from the sibling update_wishlist, but the description never names that sibling or spells out the distinction explicitly.

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?

It gives a prerequisite ('Requires sign-in') and an ownership constraint, which is real usage context. However, it offers no explicit when-to-use vs. when-not guidance and does not point to update_wishlist or create_wishlist as alternatives, leaving the agent to infer which update tool to pick.

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?