Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

List Prospect Events

list_prospect_events
Read-only

Spans every campaign by default; pass agent_id to scope to one. To page further back, re-call with before set to the oldest returned event's occurred_at. Dict with count, a summary block (replies_this_week, accepts_this_week, posts_found_this_week, meetings_booked_this_week), and an events array. Events are newest-first; each is {id, kind, channel, owner_email, occurred_at, time_precision, subject_type, snippet, turn, prospect: {id, name, linkedin_url, provider_id, title, company, has_conversation}, agent: {id, title} | null, queued_followup: {...} | null}. turn is 'user' when a draft awaits the user's approval, 'sliq' when a send is queued, else 'none'; queued_followup carries that drafted next step when one exists. prospect.id is null when the event isn't attributable to a tracked row.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindsNoSources to include — any of 'accept', 'linkedin_reply', 'email_reply'. Omit for all three.
limitNoMax events (default 50, capped at 200). Page older with `before`.
beforeNoISO 8601 timestamp cursor; only events strictly older are returned (pass a prior page's oldest `occurred_at`).
agent_idNoScope the events and the summary to one campaign. Omit for the cross-campaign feed. Note `turn` stays prospect-scoped — it can read 'user' off a draft awaiting approval under a different campaign for the same person; `queued_followup` is campaign-matched and won't.
on_behalf_ofNoA teammate's email (one with conversation sharing turned on), or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / on_behalf_of / description
      Previous value: -"Read a consented teammate's activity instead of your own —\npass their email. Gated on that teammate's conversation-sharing\nsetting; a teammate who hasn't shared is rejected. Omit for your own.\nOr pass an agency client's email, from list_agency_clients, to run the call in that client's account, where none of the teammate limits above apply."New value: +"A teammate's email (one with conversation sharing turned on), or an agency client's from list_agency_clients, to run this call in that account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
  2. Changed2 schema fields changed
    • removedInput schema / properties / as_teammate
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Read a consented teammate's activity instead of your own —\npass their email. Gated on that teammate's conversation-sharing\nsetting; a teammate who hasn't shared is rejected. Omit for your own."
-}
    • addedInput schema / properties / on_behalf_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Read a consented teammate's activity instead of your own —\npass their email. Gated on that teammate's conversation-sharing\nsetting; a teammate who hasn't shared is rejected. Omit for your own.\nOr pass an agency client's email, from list_agency_clients, to run the call in that client's account, where none of the teammate limits above apply."
+}
  3. Changed2 schema fields changed
    • addedInput schema / properties / agent_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Scope the events and the summary to one campaign. Omit for the\ncross-campaign feed. Note `turn` stays prospect-scoped — it can read\n'user' off a draft awaiting approval under a different campaign for\nthe same person; `queued_followup` is campaign-matched and won't."
+}
    • removedInput schema / properties / task_id
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "integer"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "Scope the events and the summary to one campaign. Omit for the\ncross-campaign feed. Note `turn` stays prospect-scoped — it can read\n'user' off a draft awaiting approval under a different campaign for\nthe same person; `queued_followup` is campaign-matched and won't."
-}
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=true; the description goes well beyond that by explaining the newest-first ordering, the 7-day summary payload, the default cross-campaign scope versus agent_id scoping, the `turn` semantics ('user' = draft awaiting approval, 'sliq' = send queued), and the null-prospect.id edge case. This is rich behavioral context the agent could not infer from annotations alone.

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-loaded with a tight summary sentence that captures the scope, the union of sources, and the event annotation. The returns block is long, but with no output schema it is doing necessary work; a few fields (e.g. the full event object shape) could be trimmed.

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?

With five optional parameters, no output schema, and a non-obvious cross-source result shape, the description supplies what is missing: the full return structure, the summary block contents, ordering, pagination mechanics, and scoping behavior. Nothing needed to call it correctly is absent.

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 cross-parameter interaction meaning: agent_id scopes events and the summary while `turn` remains prospect-scoped and `queued_followup` is campaign-matched. That nuance explains how parameters interact rather than merely restating defaults.

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 precise verb+resource ('Read the cross-channel prospect activity feed') and defines the resource as the newest-first union of three specific event sources. It also distinguishes itself from the alternative approach of stitching together the LinkedIn, email, and queue readers, so an agent can identify it without opening a 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 concrete triggering questions ('who replied this week', 'who's waiting on me', 'did anyone accept'), names the alternative it replaces, and specifies when to scope with agent_id versus leaving it cross-campaign. Pagination guidance ('re-call with `before` set to the oldest returned event's occurred_at') is explicit.

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

All Sliq 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