Skip to main content
Glama

HeySale — AI Website Salesperson

Create a website salesperson

create_website_salesperson
Idempotent

Give any public website an AI salesperson that talks to its visitors, answers questions about the business, and captures leads. Use this when someone wants to add a salesperson, live chat, a sales assistant or a chatbot alternative to a site. Provide the website address; the salesperson reads the site itself. The response always includes an explicit salesperson_id — keep it, because every other HeySale tool needs it — plus the one-line install script, a claim_url to give the website owner, and a private access_token — keep it and pass it to the other salesperson tools; never share it. Calling again for a website that already has a salesperson returns its id and status only. To try HeySale without touching a real website, use website_url https://hey.sale/mcp-test — that creates an isolated, disposable test salesperson on HeySale's own reviewer sandbox.

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": {
      "website_url": "<website_url>"
    },
    "name": "create_website_salesperson"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaignNo
website_urlYesThe public website address, e.g. https://example.com
business_nameNoThe business name, if known.
integration_sourceNoThe AI platform making this call, e.g. claude, chatgpt, cursor, lovable, replit.
external_project_idNoA stable id for the calling project, so repeat calls reuse the same salesperson.

Output Schema

NameRequiredDescriptionDefault
noteNo
reusedNoTrue when an existing salesperson for that website was returned instead of a new one.
statusYesBuild state of the salesperson, e.g. analyzing, building, ready, failed.
successYes
ownershipYes
expires_atNo
environmentNo
next_actionNoPlain-language next step for the caller.
preview_urlNo
salespersonYes
website_urlYes
free_minutesNo
installationYes
salesperson_idYes
salesperson_nameYes
test_environmentNo
integration_sourceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": {},
      +  "properties": {
      +    "environment": {
      +      "type": "string"
      +    },
      +    "expires_at": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "free_minutes": {
      +      "type": "number"
      +    },
      +    "installation": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "async": {
      +          "type": "boolean"
      +        },
      +        "detection": {
      +          "type": "string"
      +        },
      +        "installation_status": {
      +          "description": "What HeySale's own telemetry currently sees.",
      +          "enum": [
      +            "detected",
      +            "not_detected",
      +            "domain_mismatch",
      +            "unknown"
      +          ],
      +          "type": "string"
      +        },
      +        "placement": {
      +          "type": "string"
      +        },
      +        "review_install_url": {
      +          "description": "Sandbox only: expiring link that installs the test salesperson.",
      +          "type": "string"
      +        },
      +        "script": {
      +          "description": "The one-line script to add to the website before the closing body tag.",
      +          "type": "string"
      +        },
      +        "type": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "integration_source": {
      +      "type": "string"
      +    },
      +    "next_action": {
      +      "description": "Plain-language next step for the caller.",
      +      "type": "string"
      +    },
      +    "note": {
      +      "type": "string"
      +    },
      +    "ownership": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "claim_url": {
      +          "description": "One-time link the website owner uses to claim the salesperson. Absent once claimed.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "manage_url": {
      +          "description": "Where the owner manages the salesperson. Present once claimed.",
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "status": {
      +          "description": "Whether a HeySale account owns this salesperson yet.",
      +          "enum": [
      +            "unclaimed",
      +            "claimed"
      +          ],
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "status"
      +      ],
      +      "type": "object"
      +    },
      +    "preview_url": {
      +      "type": "string"
      +    },
      +    "reused": {
      +      "description": "True when an existing salesperson for that website was returned instead of a new one.",
      +      "type": "boolean"
      +    },
      +    "salesperson": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "domain": {
      +          "type": "string"
      +        },
      +        "id": {
      +          "description": "The salesperson_id.",
      +          "type": "string"
      +        },
      +        "name": {
      +          "type": "string"
      +        },
      +        "website_url": {
      +          "type": "string"
      +        }
      +      },
      +      "required": [
      +        "id",
      +        "name"
      +      ],
      +      "type": "object"
      +    },
      +    "salesperson_id": {
      +      "type": "string"
      +    },
      +    "salesperson_name": {
      +      "type": "string"
      +    },
      +    "status": {
      +      "description": "Build state of the salesperson, e.g. analyzing, building, ready, failed.",
      +      "type": "string"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    },
      +    "test_environment": {
      +      "type": "boolean"
      +    },
      +    "website_url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "success",
      +    "salesperson",
      +    "salesperson_id",
      +    "salesperson_name",
      +    "website_url",
      +    "status",
      +    "ownership",
      +    "installation"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • changedInput schema / properties / integration_source / description
      Previous value: -"The platform making this call, e.g. lovable."New value: +"The AI platform making this call, e.g. claude, chatgpt, cursor, lovable, replit."
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations declare non-readonly, idempotent, non-destructive, open-world, but the description adds substantial context beyond them: the exact response envelope (salesperson_id, install script, claim_url, private access_token), secret-handling obligations ('never share it'), and the deduplication behavior on repeat calls. It also notes the salesperson reads the site itself rather than requiring a supplied knowledge base.

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?

Front-loaded with purpose then when-to-use, parameter, response, and edge-case behavior in a logical progression with no filler. It is dense and long, and the response-field enumeration partially overlaps the output schema, but each sentence still conveys operational guidance an agent needs.

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 creation tool with an output schema and four annotations, the description covers everything material: what is created, what comes back, which values must be retained and passed to sibling tools, how to handle repeat calls, and how to test safely. An agent can invoke it correctly and know what to do with the result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 80%, so the schema does most of the work, but the description adds real meaning beyond it for website_url — the salesperson crawls the site, and a specific sentinel URL creates an isolated disposable test salesperson. It does not touch campaign, business_name, integration_source, or external_project_id, though the latter is already explained in its schema description.

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?

Specific verb and resource: 'Give any public website an AI salesperson that talks to its visitors, answers questions about the business, and captures leads.' This clearly distinguishes it from siblings like check_salesperson_status or configure_salesperson, which operate on an existing salesperson rather than creating one.

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?

Explicitly states when to use it ('Use this when someone wants to add a salesperson, live chat, a sales assistant or a chatbot alternative to a site') and supplies an alternative path for a non-production case via the https://hey.sale/mcp-test sandbox URL. It also states the when-not/edge case: calling again for a website that already has a salesperson returns id and status only.

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.