Skip to main content
Glama

Add to Wishfinity wishlist

add_to_wishlist
Read-only

Saves a product to the user's Wishfinity wishlist, so they can find it again, sort it into lists, and share it with friends and family. Use when the user wants to save, bookmark, remember or wishlist a product, or keep a gift idea for later (e.g. "save this for later", "add this to my wishlist", "save this as a gift idea for my mom"). Requires a specific product page URL, not a search-results or category page; if only a search page is available, ask the user for the product link. Works with any store. Wishfinity looks up the product's name, description, image and price itself when the link is opened. Returns a link the user opens to finish the save on wishfinity.com, where people without an account can sign up. Does not read or change existing lists.

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

Input Schema

NameRequiredDescriptionDefault
urlYesThe specific product page URL to save. Not a search-results or category page; if only a search page is available, ask the user for the product link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"The product page URL to save to the wishlist"New value: +"The specific product page URL to save. Not a search-results or category page; if only a search page is available, ask the user for the product link."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations say readOnlyHint=true while the description says it 'saves' a product, but the description explicitly resolves this: it returns a link the user opens to finish the save on wishfinity.com. It also discloses account sign-up for non-users, that Wishfinity looks up name/description/image/price itself, that it works with any store, and that it does not read or change existing lists.

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 is front-loaded, then intent triggers, then the URL constraint, then return behavior — a sensible order. It is slightly longer than needed because the product-page caveat is stated both in the description and in the schema's url field verbatim.

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?

For a one-parameter tool with no output schema, the description covers everything an agent needs: prerequisite input shape, what happens server-side, that the return value is a link requiring a user action, and the boundary that existing lists are untouched.

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?

With 100% schema coverage on a single required parameter, the schema already carries the semantics, and the description's URL constraint largely restates the parameter's own description text. It adds context on why (search pages can't be resolved) but no new format or syntax detail.

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?

The opening sentence gives a specific verb and resource ('Saves a product to the user's Wishfinity wishlist') and then states what that enables (find again, sort into lists, share). Because there are no siblings, no differentiation is needed, and the tool's effect is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It names the trigger intents explicitly ('save, bookmark, remember or wishlist a product', keep a gift idea) with example utterances, plus a precondition (must be a specific product page URL, not search-results/category) and a fallback ('ask the user for the product link'). When-to-use and what-to-do-when-inapplicable are both covered.

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.