Skip to main content
Glama
GrowSurf MCP Server

GrowSurf MCP Server

Official

Get Participant Activity Logs

growsurf_get_participant_activity_logs
Read-onlyIdempotent

Retrieve a participant's activity logs by GrowSurf ID or email, newest first. Use offset/limit pagination and campaign targeting to review events.

Instructions

List a participant's activity logs (by GrowSurf participant ID or email), most recent first, offset/limit paginated. limit is 1-100 (default 20); offset skips logs. The response offset is the cursor for the next page (null when there are no more). Targets campaignId if you pass it, otherwise GROWSURF_CAMPAIGN_ID.

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
campaignIdYesTarget program id for this call: the `id` returned by `growsurf_list_campaigns`, not the program name or a share URL. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server.
participantIdNo
participantEmailNo

Output Schema

NameRequiredDescriptionDefault
limitNoNumber of activity logs returned per page.
offsetNoOffset for the next page, or `null` when there are no more logs.
activityLogsNoActivity log entries for the participant.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.19.33
    • changedInput schema / properties / campaignId / description
      Previous value: -"Target program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server."New value: +"Target program id for this call: the `id` returned by `growsurf_list_campaigns`, not the program name or a share URL. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server."
  2. Changed2 schema fields changedv0.19.15
    • addedInput schema / properties / campaignId / minLength
      Added value: +1
    • addedInput schema / required
      Added value: +[
      +  "campaignId"
      +]
  3. Changed1 schema field changedv0.19.9
    • changedInput schema / properties / campaignId / description
      Previous value: -"Target program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Pass the `id` returned by growsurf_create_campaign to configure or operate a program you just created, without restarting the server."New value: +"Target program (campaign) id for this call. Defaults to GROWSURF_CAMPAIGN_ID when omitted. Program IDs also identify newly created programs without restarting the server."
  4. First observedv0.12.2

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description still earns credit by adding ordering ('most recent first'), pagination behavior, the default page size, and the fact that response offset is the next-page cursor and null at the end. It does not cover auth requirements or rate limits, but those are not central for a read-only list.

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?

Dense and front-loaded: purpose, ordering, pagination, limits and campaign targeting each get one clause with no filler. The final sentence on campaign resolution is slightly compressed but still readable.

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 needn't be spelled out, yet the description still explains the meaningful response field (offset cursor). The main gap is the unresolved ambiguity between the description's claim that campaignId falls back to an env var and the input schema listing campaignId as required.

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 description coverage is only 20% (only campaignId is documented in-schema), so the description must compensate and largely does: it establishes limit range 1-100 with default 20, that offset skips logs, and that either participantId or participantEmail identifies the target. It stops short of clarifying email-vs-ID precedence when both are supplied.

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?

Specific verb and resource: 'List a participant's activity logs' with the two accepted participant identifiers and sort order ('most recent first'). It is clearly distinct from the sibling getters like growsurf_get_participant or growsurf_get_participant_analytics, though it never names an alternative explicitly.

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

Usage Guidelines3/5

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

The description gives useful calling guidance — pagination via offset/limit and the campaignId-vs-GROWSURF_CAMPAIGN_ID fallback — but offers no when-to-use guidance relative to siblings (e.g., when to pull logs instead of the participant record or analytics). Usage is implied by the resource name rather than stated.

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

Deploy Server

Other Tools