Hustlin

Conversion snippet

conversion_snippet

The five-line snippet to drop into the product's signup or payment handler so it reports conversions to Hustlin with the visitor's tracking code (JavaScript, Swift and curl), plus a venture key for it, minted on demand and shown once. Put the key in the product's secrets as the env var named in the result, never in the repo. Owner only.

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": {
      "productId": "<productId>"
    },
    "name": "conversion_snippet"
  }
}

Input Schema

Name	Required	Description
`mint`	No	Mint a new venture key for the snippet and return it once (default true). false returns the snippet with the env var only, for a product that already has a key in its secrets.
`label`	No	A name for the key, e.g. 'production signup handler'.
`productId`	Yes	The product id.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), it discloses the facts an agent most needs: the key is minted on demand and shown only once, and it must go into the product's secrets under the env var named in the result, never into the repo. The one-time-display and secret-handling constraints are non-obvious behavior that the annotations alone would not convey.

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?

The return payload is front-loaded in the first clause, followed by the security instruction in a short imperative sentence. Slightly dense phrasing ('plus a venture key for it, minted on demand and shown once') but no filler sentences.

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?

With no output schema, the description must sketch the return value, and it does: snippet in three languages, a venture key, and an env var name in the result. The only gap is the exact result shape and the label parameter's effect, which is minor for a 3-parameter tool.

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 productId, mint and label are already documented, including the mint=false case. The description reinforces the mint-on-demand/shown-once semantics and the env var in the result, but adds nothing about label or productId beyond the schema, so the baseline 3 applies.

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 concrete verb and resource: it returns the five-line conversion-reporting snippet in JavaScript, Swift and curl, plus a venture key minted on demand. That is clearly distinguishable from siblings such as report_conversion, track_link or plan, which do not produce embeddable code.

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?

It says where the snippet goes (the product's signup or payment handler) and who may call it ('Owner only'), which sets the calling context. It stops short of naming when to prefer a sibling, but the usage scenario is clear enough that an agent won't confuse it with the reporting tools.

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

All Hustlin 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.