flowsery

Official

by Flowsery

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

Get Visitor Profile

get_visitor

Read-only

Retrieve a single visitor's full profile including geo, device, acquisition, activity, revenue, identity, and recent timeline. Use for specific visitor analysis by visitor ID.

Instructions

Get one visitor's full profile: geo, device, and browser identity, acquisition source, activity (visit and pageview counts, visited pages, completed goals), revenue (total, customer flag, seconds to first conversion), the identified profile (userId, name, email), and a merged timeline of pageviews, goals, and payments, newest first. Contains personal data: call it only when asked about a specific visitor and surface the minimum needed. profile is null for anonymous visitors; each list is capped at the 100 most recent items. Use the aggregate get_* tools for questions about many visitors. visitorId comes from the _fs_vid cookie or the dashboard; an unknown id, or one from another website, fails with 'Visitor not found'. Requires websiteId or domain with a workspace token.

Input Schema

TableJSON Schema

Name	Required	Description
`domain`	No	Website domain from list_websites (e.g. "example.com"). Alternative to websiteId with a workspace token.
`visitorId`	Yes	Visitor ID, the _fs_vid cookie value set by the tracking script (also shown in the dashboard visitor view)
`websiteId`	No	Website ID from list_websites. Required with a workspace token unless domain is given; ignored with a website key.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	No	Object with status and data: visitorId, identity, source, sourceIconUrl, activity, revenue, profile (null when anonymous), and activityTimeline sorted newest first.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedv0.1.1Sep 7, 2026

changedInput schema / properties / domain / description

Previous value: -"Website domain to query. Required when using a workspace token unless websiteId is provided."New value: +"Website domain from list_websites (e.g. \"example.com\"). Alternative to websiteId with a workspace token."

changedInput schema / properties / visitorId / description

Previous value: -"Visitor ID (from _fs_vid cookie)"New value: +"Visitor ID, the _fs_vid cookie value set by the tracking script (also shown in the dashboard visitor view)"

changedInput schema / properties / websiteId / description

Previous value: -"Website ID to query. Required when using a workspace token unless domain is provided."New value: +"Website ID from list_websites. Required with a workspace token unless domain is given; ignored with a website key."

changedOutput schema / properties / result / description

Previous value: -"Visitor profile with identity, traffic source, activity, revenue, identified profile fields, and an activity timeline."New value: +"Object with status and data: visitorId, identity, source, sourceIconUrl, activity, revenue, profile (null when anonymous), and activityTimeline sorted newest first."

First observedv0.1.0Sep 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already cover read-only and non-destructive behavior; the description adds meaningful context about personal data handling, privacy minimization, and the error case for invalid IDs. No contradiction with annotations.

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?

The description is longer than typical but every sentence carries useful information: profile contents, privacy caveat, list limits, aggregate-tool guidance, visitorId origin, and parameter requirements. It remains structured and readable.

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?

Provides complete operational context: what the profile contains, personal-data sensitivity, list caps, null behavior for anonymous visitors, error behavior for unknown IDs, and parameter resolution rules. No important usage context is missing.

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?

Schema covers all parameters with descriptions. The tool description adds helpful relationships and precedence rules, such as websiteId vs domain with workspace token and the ignored-with-website-key behavior, which goes beyond the schema.

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?

Clearly states the exact resource and action: retrieve one visitor's full profile. It distinguishes itself from the many aggregate get_* tools by emphasizing 'one visitor' and the singular profile scope.

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 instructs when to use this tool versus alternatives: use it only for a specific visitor, and use aggregate get_* tools for many visitors. Also documents failure conditions such as unknown visitorId or cross-website access.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.