Skip to main content
Glama

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 and the access_token returned when the salesperson was created.

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": {
      "salesperson_id": "<salesperson_id>"
    },
    "name": "verify_salesperson_installation"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoDevelopers only. Not required for setup, and never ask a website owner for one.
access_tokenNoThe private access_token returned by create_website_salesperson. Required to see details while the salesperson is unclaimed. Never share it with anyone else.
salesperson_idYesThe salesperson_id returned by create_website_salesperson.

Output Schema

NameRequiredDescriptionDefault
domainNo
statusYesBuild state of the salesperson, e.g. analyzing, building, ready, failed.
messageNo
installedNo
ownershipYes
expires_atNo
environmentNo
next_actionNoPlain-language next step for the caller.
salespersonYes
website_urlYes
last_seen_atNoWhen the script was last seen loading. Null before installation.
salesperson_idYes
detected_domainsNo
salesperson_nameYes
test_environmentNo
installation_statusNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / access_token
      Added value: +{
      +  "description": "The private access_token returned by create_website_salesperson. Required to see details while the salesperson is unclaimed. Never share it with anyone else.",
      +  "maxLength": 200,
      +  "minLength": 10,
      +  "type": "string"
      +}
    • addedInput schema / properties / api_key
      Added value: +{
      +  "description": "Developers only. Not required for setup, and never ask a website owner for one.",
      +  "maxLength": 200,
      +  "minLength": 10,
      +  "type": "string"
      +}
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Changed1 schema field changed
    • 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"
      +}
  4. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real value beyond them by explaining that verification relies on HeySale's own telemetry and works with single-page apps, tag managers and deferred script loading, plus the note that access_token is needed to see details while the salesperson is unclaimed.

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?

Three sentences, front-loaded with the verification purpose, followed by the mechanism and the required inputs. No sentence is filler and the anti-pattern warning is placed where it will be read.

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?

An output schema exists and annotations carry the safety profile, so the description needn't explain return values. It covers mechanism and inputs well; the only gap is not positioning the tool relative to the similarly named status/installation siblings.

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%, so all three parameters are already documented in the schema, including the api_key caveat and the access_token dependency. The description only repeats which two values to supply, adding little meaning beyond the schema; baseline 3 applies.

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 gives a specific verb and resource: checking whether a salesperson is installed on its website and reporting telemetry back to HeySale. It is clearly a verification/read operation, but it does not distinguish itself from close siblings such as check_salesperson_status 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 Guidelines3/5

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

It gives an explicit negative guideline ('never scrape the website's HTML to answer this'), which tells the agent which approach to avoid, but it names no alternative tool or condition for choosing between verify_salesperson_installation and its siblings. Usage is therefore implied rather than routed.

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.