HeySale — AI Website Salesperson

Check a salesperson's readiness

check_salesperson_status

Read-onlyIdempotent

Find out whether a website salesperson has finished reading the website and is ready to talk to visitors, and whether its script has been detected on the live site. Give it the salesperson_id returned when the salesperson was created.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`salesperson_id`	Yes	The salesperson_id returned by create_website_salesperson.

Output Schema

TableJSON Schema

Name	Required	Description
`domain`	No
`status`	Yes	Build state of the salesperson, e.g. analyzing, building, ready, failed.
`installed`	No
`ownership`	Yes
`expires_at`	No
`environment`	No
`next_action`	No	Plain-language next step for the caller.
`salesperson`	Yes
`website_url`	Yes
`last_seen_at`	No	When the script was last seen loading. Null before installation.
`salesperson_id`	Yes
`detected_domains`	No
`salesperson_name`	Yes
`test_environment`	No
`installation_status`	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": {
+    "detected_domains": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "domain": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "environment": {
+      "type": "string"
+    },
+    "expires_at": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "installation_status": {
+      "enum": [
+        "detected",
+        "not_detected",
+        "domain_mismatch",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "installed": {
+      "type": "boolean"
+    },
+    "last_seen_at": {
+      "description": "When the script was last seen loading. Null before installation.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "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"
+    },
+    "test_environment": {
+      "type": "boolean"
+    },
+    "website_url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "salesperson",
+    "salesperson_id",
+    "salesperson_name",
+    "website_url",
+    "status",
+    "ownership"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 8, 2026

changedInput schema / properties / salesperson_id / description

Previous value: -"The id returned when the salesperson was created."New value: +"The salesperson_id returned by create_website_salesperson."

First observedSep 8, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The annotations already cover the safety profile: read-only, idempotent, and non-destructive. The description adds the concrete things it checks, but does not disclose anything else about behavior or consequences. Since annotations carry most of the burden here, the added value is adequate but not outstanding.

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?

The description is concise, front-loaded with the purpose, and each sentence earns its place. It states what the tool checks and how to supply the ID without unnecessary details.

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 one-parameter read-only status check with a fully documented schema, an output schema, and safety annotations, this description is sufficient. It could be slightly stronger by explicitly steering the agent away from sibling status/verification tools, but that is already accounted for in the usage dimension.

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%, and the salesperson_id parameter is already clearly documented. The description repeats that the ID comes from creation, which is helpful but does not add meaningful semantic information beyond the schema.

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?

The description states a specific outcome — checking whether the salesperson has finished reading the website and whether its script is detected on the live site. It is clear, but it does not explicitly distinguish itself from overlapping siblings like verify_salesperson_installation or get_salesperson_installation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description only instructs the agent to pass the salesperson_id returned at creation. It provides no guidance about when to prefer this tool over siblings such as verify_salesperson_installation or get_salesperson_results, and no when-not-to-use guidance.

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.