HeySale — AI Website Salesperson

Change how a salesperson introduces itself

configure_salesperson

Idempotent

Change a salesperson's name, its opening line, or the goal it works towards. While a salesperson is still unclaimed this can be set as part of setting it up. Once the website owner has claimed it, changes must be made by the owner in HeySale — do not ask anyone for an API key.

Input Schema

TableJSON Schema

Name	Required	Description
`name`	No
`api_key`	No	Developers only. Not required, and never ask a website owner for one.
`greeting`	No
`objective`	No	What the salesperson should aim for.
`salesperson_id`	Yes	The salesperson_id returned by create_website_salesperson.

Output Schema

TableJSON Schema

Name	Required	Description
`status`	Yes	Build state of the salesperson, e.g. analyzing, building, ready, failed.
`message`	No
`success`	No
`updated`	No	Which fields were changed.
`ownership`	Yes
`error_code`	No
`expires_at`	No
`environment`	No
`next_action`	No	Plain-language next step for the caller.
`salesperson`	Yes
`website_url`	Yes
`salesperson_id`	Yes
`salesperson_name`	Yes
`test_environment`	No
`authentication_required`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "additionalProperties": {},
+  "properties": {
+    "authentication_required": {
+      "type": "boolean"
+    },
+    "environment": {
+      "type": "string"
+    },
+    "error_code": {
+      "type": "string"
+    },
+    "expires_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "message": {
+      "type": "string"
+    },
+    "next_action": {
+      "description": "Plain-language next step for the caller.",
+      "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"
+    },
+    "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"
+    },
+    "updated": {
+      "description": "Which fields were changed.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "website_url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "salesperson",
+    "salesperson_id",
+    "salesperson_name",
+    "website_url",
+    "status",
+    "ownership"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedSep 8, 2026

changedInput schema / properties / api_key / description

Previous value: -"The owner's HeySale API key, from their dashboard."New value: +"Developers only. Not required, and never ask a website owner for one."

addedInput schema / properties / salesperson_id / description

Added value: +"The salesperson_id returned by create_website_salesperson."

changedInput schema / required

Previous value: -[
-  "salesperson_id",
-  "api_key"
-]New value: +[
+  "salesperson_id"
+]

First observedSep 8, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description adds valuable behavioral context beyond the annotations: ownership state changes the permitted workflow, and API keys must not be requested from website owners. This goes well beyond the schema and complements the readOnlyHint=false and idempotentHint=true annotations without contradicting them.

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?

Two focused sentences deliver the core purpose and the key usage boundary without repetition or filler. The most important information is front-loaded and every clause adds value.

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?

The description covers what the tool changes, when it should be used, when it should not be used, and how to handle API keys. An output schema exists, so return values do not need to be described. Given the tool's moderate complexity, nothing critical is missing.

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?

The description maps 'name', 'opening line', and 'goal' to the likely parameters name, greeting, and objective, adding meaning not fully explicit in the schema. The api_key and salesperson_id parameters are already documented in the schema, and the description reinforces the API key policy, though it does not explain every parameter.

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 description states a specific action ('Change') and clearly identifies the resources being modified: the salesperson's name, opening line, and goal. It is easy to distinguish from sibling tools like create_website_salesperson or check_salesperson_status because it focuses on modifying an existing salesperson's configuration.

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?

The description gives clear when-to-use guidance: configure while the salesperson is unclaimed, as part of setup. It also gives a when-not-to-use rule: once claimed, changes must be made by the owner in HeySale. It does not explicitly name an alternative tool like create_website_salesperson, but the context is sufficient.

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

All HeySale — AI Website Salesperson 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.