Skip to main content
Glama

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.

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": "get_salesperson_results"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNo
api_keyNoDevelopers only. Not required for setup, and never ask a website owner for one.
salesperson_idYesThe salesperson_id returned by create_website_salesperson.

Output Schema

NameRequiredDescriptionDefault
noteNo
leadsNo
statusYesBuild state of the salesperson, e.g. analyzing, building, ready, failed.
ownershipYes
syntheticNoTrue when the figures come from the reviewer sandbox.
expires_atNo
environmentNo
next_actionNoPlain-language next step for the caller.
period_daysNo
salespersonYes
website_urlYes
recent_leadsNo
talk_minutesNo
conversationsNo
top_questionsNo
salesperson_idYes
conversion_rateNo
salesperson_nameYes
test_environmentNo
authentication_requiredNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changed
    • 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"
      +}
  3. Changed3 schema fields changed
    • 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"
      +]
  4. First observed

TDQS

A3.5/5.0
Behavior3/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 safety is covered elsewhere. The description does add a real behavioral fact beyond that: the data is private and only returned to an authorised caller, and the caller must never solicit an API key from a website owner. It says nothing about the time window behavior or aggregation semantics.

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?

Two sentences, front-loaded with the capability before the privacy caveat, with no filler. The auth sentence is somewhat long relative to the capability statement but carries non-obvious policy information, so it earns its place.

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?

With annotations covering the safety profile and an output schema covering return values, the definition only needs to establish purpose and auth posture, both of which it does. The remaining gap is the unexplained `days` window, which leaves the agent guessing about the default time range.

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 coverage is 67%, with salesperson_id and api_key already documented in the schema, so baseline 3 applies. The description contributes nothing beyond that — notably the `days` parameter (1-90) is never explained, so the agent gets no idea what window the summary covers or whether a default exists.

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 gives a specific verb ("Summarise") and enumerates the exact metrics returned: visitor conversations, leads captured, and most-asked-about topics for a given salesperson. That metric set inherently separates it from the sibling tools (installation, status, configure, create), so an agent can pick it without opening the schema.

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?

There is no guidance on when to call this versus check_salesperson_status or get_salesperson_installation, and no prerequisite is stated. The only conditional language concerns API keys, which is an authentication rule rather than a selection rule.

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.