Skip to main content
Glama

HeySale — AI Website Salesperson

Change how a salesperson introduces itself

configure_salesperson
Idempotent

Change a salesperson's name, its opening line, or the goal it works towards. While a salesperson is still unclaimed this can be set as part of setting it up. Once the website owner has claimed it, changes must be made by the owner in HeySale — do not ask anyone for an API key.

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

Input Schema

NameRequiredDescriptionDefault
nameNo
api_keyNoDevelopers only. Not required, and never ask a website owner for one.
greetingNo
objectiveNoWhat the salesperson should aim for.
salesperson_idYesThe salesperson_id returned by create_website_salesperson.

Output Schema

NameRequiredDescriptionDefault
statusYesBuild state of the salesperson, e.g. analyzing, building, ready, failed.
messageNo
successNo
updatedNoWhich fields were changed.
ownershipYes
error_codeNo
expires_atNo
environmentNo
next_actionNoPlain-language next step for the caller.
salespersonYes
website_urlYes
salesperson_idYes
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"
      +    },
      +    "environment": {
      +      "type": "string"
      +    },
      +    "error_code": {
      +      "type": "string"
      +    },
      +    "expires_at": {
      +      "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"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    },
      +    "test_environment": {
      +      "type": "boolean"
      +    },
      +    "updated": {
      +      "description": "Which fields were changed.",
      +      "items": {
      +        "type": "string"
      +      },
      +      "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, 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

A4.1/5.0
Behavior4/5

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

Annotations declare a non-destructive, idempotent write; the description adds the crucial behavioral fact that usability is gated on claim state and that post-claim edits are impossible through this tool. It stops short of saying what error or response results from a blocked call, but the operational constraint is disclosed.

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 mutated fields before the eligibility rule. Every clause carries information; only the api_key deterrent is slightly redundant with the schema description.

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, so return values need not be explained, and the annotations cover safety. The remaining gap is whether omitted fields are left untouched versus cleared, which matters for an idempotent partial update.

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?

With 60% schema coverage, the description usefully maps greeting to 'opening line' and objective to 'the goal it works towards', and reinforces the api_key warning already in the schema. It adds little for salesperson_id beyond what the schema's description already provides, and says nothing about partial updates.

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?

States a specific verb and resource plus the three mutable fields (name, opening line, goal), so an agent knows exactly what is modified. It does not explicitly contrast itself with create_website_salesperson, though the 'while unclaimed this can be set as part of setting it up' clause hints at that boundary.

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

Usage Guidelines5/5

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

Explicitly states when the tool applies (unclaimed salesperson, during setup) and when it does not (after the owner claims it, changes must happen in HeySale). It adds a concrete prohibition - do not ask anyone for an API key - which prevents a common wrong turn.

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.