Skip to main content
Glama
Sign In

Hustlin

by ai.hustlin
OverviewDiscussionsAdmin

Create a product

create_product

Add a product to Hustlin from its name, description and URL. Returns the new product id. Counts against the plan's product limit. Fields and the HUSTLIN.md template: https://hustlin.ai/mcp.

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>",
      "description": "<description>"
    },
    "name": "create_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoThe product's public URL, if it has one.
modeNoPermission mode. Default approve.
stageNoWhere the product is.
titleYesProduct name.
pricingNoHow it makes money, e.g. 'Free tier, $29/mo Pro'.
descriptionYesWhat it does and for whom, in plain words (the README's first paragraph is a good start).
targetAudienceNoWho buys it (the ICP).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses two useful behavioral facts: the response contains the new product id, and the call consumes a metered plan quota. It does not explain what `mode` (observe/approve/auto) does in practice or whether the write is reversible, so it stops short of full disclosure.

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 compact sentences, front-loaded with the action and the return value, with the quota warning given its own sentence. The final fragment ("Fields and the HUSTLIN.md template: <url>") is terse to the point of ambiguity about what the reader will find there.

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 7-parameter mutation tool with no output schema, the description supplies the two things the structured data cannot: the return value and the quota cost. Remaining gaps (enum behavior for `mode`, duplicate handling) are modest and partially mitigated by rich schema descriptions.

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 schema already documents all seven parameters including enum meanings and length limits. The description only names three of them (name, description, URL) and adds no syntax, defaults, or interaction detail beyond the schema; the HUSTLIN.md link is a pointer, not added semantics.

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 ("Add a product to Hustlin") plus the identifying inputs and the return value ("Returns the new product id"). It is clear on its own, but it never contrasts itself with the sibling `products` tool, so an agent must infer the listing-vs-creating split.

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?

Usage context is implied rather than stated: it is obviously the creation path, and "Counts against the plan's product limit" warns of a cost. There is no explicit when-to-use guidance and no mention of what to do if the product already exists or how it relates to `products`/`plan`.

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

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