Skip to main content
Glama

funn.to Funnel Generator

by to.funn
OverviewDiscussionsAdmin

generate_funnel

Generate a hosted Amazon affiliate landing page from a US amazon.com product URL the user gave you. One call takes ~4 minutes and costs real money, with no undo and no refund, so call it only for a link the user actually supplied. Never build a URL from an ASIN you remember, and never submit an example URL. If you do not have the user's link, ask for it instead of calling. No account needed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
axesNoStyle axes, all 0-100, omitted default to 50. Use list_axes for details.
store_idNoThe user's own Amazon Associates Store ID, if they gave it to you in this conversation (US tags end in -20). Omit it when unsure. Never guess one and never reuse a tag from an example or another conversation: a wrong tag pays the user's commissions to somebody else. It can be added later at https://funn.to.
amazon_urlYesThe amazon.com product URL exactly as the user gave it to you: copy it, do not retype or reconstruct it. Shape: https://www.amazon.com/<product-slug>/dp/<ASIN> or https://www.amazon.com/dp/<ASIN>. There is deliberately no example ASIN here: example ASINs get submitted as real products and bill the user for a page about something nobody asked for. If the user has not given you a link, ask for one rather than composing it from an ASIN you recall.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / amazon_url / description
      Previous value: -"Amazon product URL (e.g. https://www.amazon.com/dp/B0DWN2KR9W)"New value: +"The amazon.com product URL exactly as the user gave it to you: copy it, do not retype or reconstruct it. Shape: https://www.amazon.com/<product-slug>/dp/<ASIN> or https://www.amazon.com/dp/<ASIN>. There is deliberately no example ASIN here: example ASINs get submitted as real products and bill the user for a page about something nobody asked for. If the user has not given you a link, ask for one rather than composing it from an ASIN you recall."
    • changedInput schema / properties / amazon_url / pattern
      Previous value: -"^https?:\\/\\/(www\\.)?amazon\\.(com|co\\.uk|de|fr|it|es|ca|com\\.au|co\\.jp|in|com\\.br|com\\.mx|nl|sg|ae|sa|pl|se|com\\.be|com\\.tr)(\\/|$)"New value: +"^https?:\\/\\/(www\\.)?amazon\\.com\\/"
    • changedInput schema / properties / store_id / description
      Previous value: -"Amazon Associates Store ID (e.g. mystore-20). Optional."New value: +"The user's own Amazon Associates Store ID, if they gave it to you in this conversation (US tags end in -20). Omit it when unsure. Never guess one and never reuse a tag from an example or another conversation: a wrong tag pays the user's commissions to somebody else. It can be added later at https://funn.to."
  2. Changed3 schema fields changed
    • addedInput schema / properties / axes / properties / factness
      Added value: +{
+  "description": "0=Anchored, 100=Fictional",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / axes / properties / format
      Added value: +{
+  "description": "0=Sales page, 100=Blog review",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "number"
+}
    • addedInput schema / properties / axes / properties / persona
      Added value: +{
+  "description": "0=Third person, 100=First person",
+  "maximum": 100,
+  "minimum": 0,
+  "type": "number"
+}
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description fully discloses the critical behavioral traits: ~4-minute latency, real monetary cost, no undo, and no refund. It also states that no account is needed, covering the main operational risks an agent must know before invoking.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A few short sentences, with the core action first and the critical warnings following. Every sentence carries risk-relevant or scoping information; nothing is redundant filler.

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?

The description covers the preconditions, costs, latency, and irreversibility needed to invoke safely. It does not explicitly describe what the call returns or how it connects to get_funnel_status, but the absence of an output schema and the presence of a status sibling make this a minor gap rather than a fatal one.

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% and the schema's own descriptions already explain the URL shape, the store_id policy, and axes defaults, so the description doesn't need to add parameter-level detail. The description reinforces sourcing rules but adds no new semantic meaning for the parameters themselves.

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 states a specific action ('Generate'), a specific deliverable ('hosted Amazon affiliate landing page'), and an exact input source (a US amazon.com product URL supplied by the user). This makes the tool's role immediately distinguishable from the sibling status/axes tools.

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?

Calls out the precise precondition ('only for a link the user actually supplied') and the disqualifying cases (never reconstruct from a remembered ASIN, never submit an example URL), with the alternative action ('ask for it instead of calling') stated explicitly. This is clear when-to and when-not-to guidance.

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

All funn.to Funnel Generator toolsInspect
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