Skip to main content
Glama

Get a contact's journey

get_contact_journey
Read-onlyIdempotent

How one contact found the business: every ad, campaign or referring site that brought them back (oldest first, e.g. Google ad → Facebook ad → newsletter → enquiry), the pages they read, and what they did — forms, orders, sales the owner recorded offline. Use for "tell me about this person's journey", "which ad did they come from". Get the id from list_contacts. Answer from summary; never add steps it does not contain. PERSONAL DATA — same handling rules as list_contacts.

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": {
      "site_id": "<site_id>",
      "contact_id": "<contact_id>"
    },
    "name": "get_contact_journey"
  }
}

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site the contact belongs to
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
contact_idYesContact id, from list_contacts

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
      +  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already identify this as a read-only, idempotent, non-destructive operation. The description adds useful behavior: results are oldest first, the answer should come from `summary`, and the agent must not invent steps. It also flags personal-data handling, though it does not discuss pagination or response size.

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 dense but well structured: it front-loads what the journey contains, then gives usage examples, prerequisite ID source, output constraint, and data-handling note. Every clause adds useful context and there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only tool with full schema coverage and no output schema, the description supplies the missing behavioral context: what the journey includes, its ordering, how to answer from `summary`, and personal-data handling. An agent has enough information to select and invoke it correctly.

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 itself. The description reinforces that contact_id comes from list_contacts, but that is already in the schema and it adds no additional parameter meaning beyond the structured fields.

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 resource and scope: one contact's acquisition journey, including ads, campaigns, referring sites, pages read, and actions. It clearly differentiates this from a general contact lookup or journey-definition tool by focusing on how the contact found the business.

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?

It gives concrete use cases such as 'tell me about this person's journey' and 'which ad did they come from', and tells the agent to get the id from list_contacts. It does not explicitly state when not to use it or name a direct alternative, so it stops short of full when/when-not guidance.

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.

Resources