HeySale — AI Website Salesperson

Verify a salesperson's website installation

verify_salesperson_installation

Read-onlyIdempotent

Check whether a HeySale salesperson has actually been installed on its website and is reporting back to HeySale. Uses HeySale's own telemetry, so it works with single-page apps, tag managers and deferred script loading — never scrape the website's HTML to answer this. 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.
`message`	No
`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"
+      ]
+    },
+    "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"
+    },
+    "test_environment": {
+      "type": "boolean"
+    },
+    "website_url": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "salesperson",
+    "salesperson_id",
+    "salesperson_name",
+    "website_url",
+    "status",
+    "ownership"
+  ],
+  "type": "object"
+}

AddedSep 8, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already signal read-only, idempotent, non-destructive behavior. The description adds meaningful behavioral detail: it relies on HeySales telemetry, works across modern tag-manager setups, and explicitly warns against scraping. This goes beyond the 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 sentences carry a clear purpose, a scoping instruction, and an explicit anti-pattern warning. Every clause earns its place and the core action is front-loaded.

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 simple verification tool with one parameter, the description covers what it checksाक and how it checks it. It does not describe the return value, but no output schema was provided; still, the phrasing 'has actually been installed and is reporting back' strongly implies a boolean 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?

The input schema fully documents the single UUID parameter, so baseline is 3. The description adds the useful provenance detail that salesperson_id comes from creation-time response, which helps the agent know where to source the value.

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—'Check whether a HeySales salesperson has actually been installed on its website and is reporting back to HeySales'—which makes the tool's purpose unmistakable. It also distinguishes this verification goal from a generic status lookup by emphasizing actual installation and reporting.

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 operational guidance: use HeySales' telemetry rather than scraping, and handle SPA/tag manager/deferred loading scenarios. It does not explicitly contrast this tool with siblings like get_salesperson_installation or check_salesperson_status, so the differentiation is implicit rather than named.

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.