Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

List Sent Messages

list_sent_messages
Read-only

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoCase-insensitive text to find in the message or the recipient's name.
limitNoPage size, at most 200.
offsetNoPage offset. `total` is the count before paging, so the whole tail is reachable.
originNo'sliq' for messages to prospects only, 'imported' for imported conversations only; omit for both.
tag_idNoOnly messages carrying this tag (from list_message_tag_groups); takes precedence over tag_state.
sendersNoIn a shared workspace, the teammate emails (yours included, if wanted) whose messages to list; omit for only your own. A teammate who doesn't share conversations, or an email outside the workspace, is dropped; if none remain the list is empty.
positionsNo'first', 'follow_up' and/or 'reply' to narrow by message type; omit for all. A connection-request note is always 'first'.
tag_stateNo'all', 'tagged' (at least one tag in any group) or 'untagged' (no tags; a "No match" result counts as untagged).all
prospect_idNoOnly messages sent to this prospect.
provider_idNoOnly LinkedIn messages sent to this LinkedIn provider id — how to list an imported conversation's messages, which have no prospect_id.
on_behalf_ofNoAn agency client's email, from list_agency_clients, to run this call in that client's 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
    • addedInput schema / properties / on_behalf_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "An agency client's email, from list_agency_clients, to run this call in that client's account: their agents, settings, connected accounts, and credits. Omit it to act on your own account."
+}
  2. Changed4 schema fields changed
    • addedInput schema / properties / origin
      Added value: +{
+  "anyOf": [
+    {
+      "description": "Whose conversation a sent message belongs to: a Sliq prospect's, or an imported one — a\nLinkedIn conversation the user started with someone who has no prospect row. An origin filter\nis one of these, None for both.",
+      "enum": [
+        "sliq",
+        "imported"
+      ],
+      "title": "Origin",
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "'sliq' for messages to prospects only, 'imported' for imported conversations\nonly; omit for both."
+}
    • changedInput schema / properties / positions / anyOf
      Previous value: -[
-  {
-    "items": {
-      "description": "A send's spot in its conversation; a positions filter is a list of these, None for all.\nThe conversation's first outbound send is 'first', a later one sent before the prospect's\nfirst reply is 'follow_up', and any send after that reply is 'reply'. Derived, never stored\nper message.",
-      "enum": [
-        "first",
-        "follow_up",
-        "reply"
-      ],
-      "title": "Position",
-      "type": "string"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "description": "A send's spot in its conversation; a positions filter is a list of these, None for all.\nThe conversation's first outbound send is 'first', a later one sent before the other person's\nfirst reply is 'follow_up', and any send after that reply is 'reply'. Derived, never stored\nper message.",
+      "enum": [
+        "first",
+        "follow_up",
+        "reply"
+      ],
+      "title": "Position",
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / provider_id
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Only LinkedIn messages sent to this LinkedIn provider id — how to list an\nimported conversation's messages, which have no prospect_id."
+}
    • changedInput schema / properties / q / description
      Previous value: -"Case-insensitive text to find in the message or the prospect's name."New value: +"Case-insensitive text to find in the message or the recipient's name."
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

With readOnlyHint already declaring safety, the description still adds substantial non-obvious behavior: default is the user's own messages only, `senders` expands to teammates, shared-agent calls are scoped to that agent's campaign, imported messages have null prospect_id and are addressed via person.provider_id, and `outcome` is the prospect's funnel stage rather than the message's effect. This is rich context beyond the annotation.

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?

Content is front-loaded and sectioned into summary and returns, and the length is largely justified by 11 parameters and no output schema. The opening sentence is a dense run-on with nested parentheticals that could be broken up, costing a point.

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 an 11-parameter, read-only list tool with no output schema, the definition covers filtering, scoping, and the full return shape (counts, message fields, tags, groups, outcome, look_up banner) including edge cases like imported conversations and in-progress lookups. Nothing an agent needs to call it correctly is missing.

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 every parameter is already documented in the schema. The description only restates a few of them (senders for teammates, tag_state='untagged') without adding syntax or semantics the schema lacks, so the baseline 3 applies.

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 precise verb+resource and scope: every message the user sent, to a prospect or in an imported LinkedIn conversation, with all tag-group tags, mirroring the Analytics → Messages tab. It clearly distinguishes itself from siblings by naming correct_message_classification, list_message_tag_groups, and look_up_imported_people as related but distinct.

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?

It explicitly enumerates when to use it ('to see which messages have no tags yet (tag_state='untagged')', 'to read a message's tags across all groups at once', 'to find a message to tag with correct_message_classification') and gives the condition that routes to the alternative. It also states the shared-agent scoping caveat.

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