Skip to main content
Glama
Sign In

Sliq

by com.getsliq
OverviewDiscussionsAdmin

List inbox conversations

list_inbox_conversations
Read-only

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_inbox_conversations"
  }
}

Input Schema

NameRequiredDescriptionDefault
tabNoWhich Inbox tab to read. Omit for every conversation.
limitNoMax conversations per page (default and max 50).
offsetNoConversations to skip for paging; while has_more is true, re-call with offset advanced by the number of conversations returned.
agent_idNoOnly that campaign's prospects. Omit for the whole Inbox.
on_behalf_ofNoA teammate's email, 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: -"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."New value: +"A teammate's email, 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. Changed1 schema field changed
    • changedInput schema / properties / tab / anyOf
      Previous value: -[
-  {
-    "description": "The Inbox tab a conversation sits in. your_turn: they wrote last and no reply\nis queued. follow_up: they have written to us before, we wrote last, and nothing\nis queued.",
-    "enum": [
-      "your_turn",
-      "follow_up"
-    ],
-    "title": "InboxTab",
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "The Inbox tab a conversation sits in. your_turn: they wrote last and no reply\nis queued or scheduled. follow_up: they have written to us before, we wrote last,\nand nothing is queued or scheduled.",
+    "enum": [
+      "your_turn",
+      "follow_up"
+    ],
+    "title": "InboxTab",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  3. Changed9 schema fields changed
    • addedInput schema / properties / limit
      Added value: +{
+  "default": 50,
+  "description": "Max conversations per page (default and max 50).",
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "default": 0,
+  "description": "Conversations to skip for paging; while has_more is true, re-call with offset\nadvanced by the number of conversations returned.",
+  "type": "integer"
+}
    • addedInput schema / properties / tab / anyOf
      Added value: +[
+  {
+    "description": "The Inbox tab a conversation sits in. your_turn: they wrote last and no reply\nis queued. follow_up: they have written to us before, we wrote last, and nothing\nis queued.",
+    "enum": [
+      "your_turn",
+      "follow_up"
+    ],
+    "title": "InboxTab",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / tab / default
      Added value: +null
    • changedInput schema / properties / tab / description
      Previous value: -"Which Inbox tab to read."New value: +"Which Inbox tab to read. Omit for every conversation."
    • removedInput schema / properties / tab / enum
      Removed value: -[
-  "your_turn",
-  "follow_up"
-]
    • removedInput schema / properties / tab / title
      Removed value: -"InboxTab"
    • removedInput schema / properties / tab / type
      Removed value: -"string"
    • removedInput schema / required
      Removed value: -[
-  "tab"
-]
  4. Added

TDQS

A4.4/5.0
Behavior3/5

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

The readOnlyHint=true annotation is consistent with a listing tool, and the description adds real behavioral context beyond it: result ordering (due reminders first, then newest message first) and the fact that hidden/dismissed conversations are still returned. However, much of that behavioral detail is packed into the returns block rather than the summary, and it doesn't mention rate limits or per-account cost implications of `on_behalf_of`.

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 summary is front-loaded and task-oriented, and the returns block is justified because no output schema exists. It is still lengthy — the scheduled_replies status enumeration and field-by-field glossary could be tightened — but nearly every sentence carries operational information rather than restating the name.

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 no output schema, the tool carries the full burden of describing the return shape, and it does so: envelope fields, per-conversation fields, enum meanings for tab/visibility/reply_outcome/status, and the cross-reference that person_id is query_people's id. Combined with tab routing and paging notes, an agent has everything needed to call and interpret the result.

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 100%, so the baseline is 3, but the description adds meaning the schema doesn't: that omitting `tab` returns conversations in *neither* tab (the All view including hidden ones), a nuance the schema's 'Omit for every conversation' only hints at. It does not elaborate on `agent_id` or `on_behalf_of`, leaving those to 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?

The summary opens with a specific verb+resource ('Read the user's Sliq Inbox') and immediately grounds it in a familiar referent ('the same lists the Inbox page shows'). It then distinguishes the scope of each mode and names the sibling tool (get_pending_approvals) that covers the adjacent content, so an agent can place this tool without opening the 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?

Explicit routing rules: `tab='your_turn'` for 'who's waiting on me', `tab='follow_up'` for 'who should I follow up with' or 'who went quiet', and omit `tab` for every conversation including those in neither tab. It also states an exclusion — drafts and approvals come from get_pending_approvals instead — which is exactly the when-not guidance most definitions lack.

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