Skip to main content
Glama

Flowsery

by com.flowsery
OverviewDiscussionsAdmin

Get Visitor Profile

get_visitor
Read-only

Get the analytics for one visitor to the user's own website: country and city, device and browser, acquisition source, activity (visit and pageview counts, visited pages, completed goals), revenue totals, whether the visitor is identified, and a timeline of pageviews, goals, and purchase amounts, newest first. Names, emails, user IDs, IP addresses, and card or billing details are never returned. Call it only when the user asks about a specific visitor, and share only what answers the question. 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 is the visitor record ID from get_realtime_map or the dashboard visitor view, not the _fs_vid cookie value; an unknown id, or one from another website, fails with 'Visitor not found'. Requires websiteId or domain with a workspace token.

Input Schema

NameRequiredDescriptionDefault
domainNoWebsite domain from list_websites (e.g. "example.com"). Alternative to websiteId with a workspace token.
visitorIdYesVisitor record ID from get_realtime_map or the dashboard visitor view (not the _fs_vid cookie value)
websiteIdNoWebsite ID from list_websites. Required with a workspace token unless domain is given; ignored with a website key.
workspaceIdNoWorkspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another

Output Schema

NameRequiredDescriptionDefault
resultNoObject with status and data: visitorId, identity, source, sourceIconUrl, activity, revenue, profile ({ identified: true } for identified visitors, null when anonymous; no names, emails or user IDs), and activityTimeline sorted newest first.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / result / description
      Previous value: -"Object with status and data: visitorId, identity, source, sourceIconUrl, activity, revenue, profile (null when anonymous), and activityTimeline sorted newest first."New value: +"Object with status and data: visitorId, identity, source, sourceIconUrl, activity, revenue, profile ({ identified: true } for identified visitors, null when anonymous; no names, emails or user IDs), and activityTimeline sorted newest first."
  2. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • removedOutput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. Changed1 schema field changed
    • addedInput schema / properties / workspaceId
      Added value: +{
+  "description": "Workspace to act in: an id from list_workspaces. Omit to use the default workspace. Use the same workspaceId for every call about the same workspace, since ids from one workspace do not exist in another",
+  "type": "string"
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / visitorId / description
      Previous value: -"Visitor ID, the _fs_vid cookie value set by the tracking script (also shown in the dashboard visitor view)"New value: +"Visitor record ID from get_realtime_map or the dashboard visitor view (not the _fs_vid cookie value)"
  5. Changed4 schema fields changed
    • 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."
  6. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the readOnly/destructive annotations: it commits to never returning names, emails, user IDs, IPs, or billing details, discloses that profile is null for anonymous visitors, notes the 100-item cap on each list, and specifies the exact failure string for an unknown or cross-website id. This is rich operational context for a read tool.

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?

Front-loads the returned data, then constraints, then usage routing — a sensible ordering with no filler sentences. It is on the long side, and enumerating return fields is partly redundant given an output schema exists, which keeps it out of the top score.

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?

Covers auth requirements, id provenance, error behavior, list caps, anonymous-visitor nulls, and privacy scope. Since an output schema exists, the description is not obligated to explain return shapes, and nothing an agent needs to call or interpret this tool 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 coverage is already 100%, so the baseline is 3, but the description adds genuine value: it disambiguates visitorId from the _fs_vid cookie value and points to where a valid id comes from (get_realtime_map or the dashboard view), and it restates the websiteId/domain workspace-token requirement. It adds meaning beyond the schema fields rather than repeating them.

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?

States a specific verb (get) and resource (analytics for one visitor to the user's own website), then enumerates the returned dimensions (geo, device, acquisition, activity, revenue, timeline). It explicitly contrasts itself with the aggregate get_* sibling tools, so an agent can route correctly without opening another schema.

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?

Gives an explicit when-to-call condition ('only when the user asks about a specific visitor'), a when-not rule ('Use the aggregate get_* tools for questions about many visitors'), and a disclosure constraint ('share only what answers the question'). Alternatives are named rather than implied.

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

All Flowsery toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources