HeySale — AI Website Salesperson

See what the salesperson achieved

get_salesperson_results

Read-onlyIdempotent

Summarise how many visitors talked to the salesperson, how many left their details, and what they asked about most. This is private business data: it is only returned to an authorised caller. Never ask a website owner for an API key — send them to HeySale instead.

Input Schema

TableJSON Schema

Name	Required	Description
`days`	No
`api_key`	No	Developers only. Not required for setup, and never ask a website owner for one.
`salesperson_id`	Yes	The salesperson_id returned by create_website_salesperson.

Output Schema

TableJSON Schema

Name	Required	Description
`note`	No
`leads`	No
`status`	Yes	Build state of the salesperson, e.g. analyzing, building, ready, failed.
`ownership`	Yes
`synthetic`	No	True when the figures come from the reviewer sandbox.
`expires_at`	No
`environment`	No
`next_action`	No	Plain-language next step for the caller.
`period_days`	No
`salesperson`	Yes
`website_url`	Yes
`recent_leads`	No
`talk_minutes`	No
`conversations`	No
`top_questions`	No
`salesperson_id`	Yes
`conversion_rate`	No
`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"
+    },
+    "conversations": {
+      "type": "number"
+    },
+    "conversion_rate": {
+      "type": "number"
+    },
+    "environment": {
+      "type": "string"
+    },
+    "expires_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "leads": {
+      "type": "number"
+    },
+    "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"
+    },
+    "period_days": {
+      "type": "number"
+    },
+    "recent_leads": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "captured_at": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "company": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "email": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "interest": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "question": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status": {
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "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"
+    },
+    "synthetic": {
+      "description": "True when the figures come from the reviewer sandbox.",
+      "type": "boolean"
+    },
+    "talk_minutes": {
+      "type": "number"
+    },
+    "test_environment": {
+      "type": "boolean"
+    },
+    "top_questions": {
+      "items": {
+        "anyOf": [
+          {
+            "type": "string"
+          },
+          {
+            "additionalProperties": {},
+            "properties": {
+              "count": {
+                "type": "number"
+              },
+              "theme": {
+                "type": "string"
+              }
+            },
+            "type": "object"
+          }
+        ]
+      },
+      "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 for setup, 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.1/5.0

Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context beyond the annotations: the data is private business data and is only returned to an authorized caller, and the agent must not request an API key from a website owner. No contradiction with annotations.

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 sentences with no filler: the first states what the tool does, the other two convey security/authorization context. The api_key caution is slightly redundant with the schema's own api_key description, but the whole text is compact and front-loaded with the core behavior.

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?

Given that an output schema exists, the description does not need to explain the return shape. It provides the key behavioral gotcha (private data, authorized caller) and the sibling distinction is inferred. The days parameter lacks an example or default, but the schema maximum/minimum bounds suffice for correct calling.

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 67%, and the schema already documents salesperson_id and api_key well, including that the api_key is developers-only. The description adds some meaning by framing the API key context (private data, authorized caller, never ask the website owner), but does not explain about the days parameter, so it only partially supplements the schema.

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 names a specific verb ('Summarise') and resource (what the salesperson achieved: visitors talked, details left, top topics asked about). It clearly distinguishes itself from sibling tools like check_salesperson_status or get_salesperson_installation, which cover status or installation rather than performance results.

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 provides clear context: use it when you need a summary of salesperson results, with the important caution that this is private data only for authorized callers. It does not explicitly name when to use an alternative sibling, but the security guidance (never ask a website owner for an API key) is a clear behavioral constraint.

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.