Skip to main content
Glama
Sign In

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Get LinkedIn monitors

get_linkedin_monitors
Read-only

Default (no monitor_id): one summary per monitor with members_count (the number of watched LinkedIn profile and company page URLs — list mode only, 0 for network/topic) and members_sample (the first 5 URLs), not the full roster, since a list monitor can watch thousands. To read a monitor's full roster, pass its id (returned on each summary) as monitor_id; that returns the URL list paged by offset/limit with a truncated flag — re-call with offset += limit while truncated. The URLs are in the exact shape set_up_linkedin_monitoring takes back. run_weekdays is weekday ints Mon=0 … Sun=6 in the user's timezone. last_run_at is null before the monitor's first run. By default, a dict {'monitors': [{'id', 'name', 'mode', 'is_active', 'members_count', 'members_sample', 'keywords', 'writing_instructions', 'post_filter', 'draft_comments', 'fetch_engagers', 'capture_authors', 'engager_icp', 'engager_instructions', 'run_weekdays', 'recency_days', 'last_run_at'}, ...]} — an empty list if the agent has no monitors. With monitor_id: {'monitor_id', 'name', 'members_count', 'members' (this page's URL list), 'offset', 'limit', 'truncated'}. post_filter is the user's own description of which posts the monitor keeps (blank keeps every post). engager_icp filters who capture collects (blank means everyone) and engager_instructions is what to do with them (blank means take no action); both are blank when fetch_engagers and capture_authors are both off, and both need re-passing when re-arming capture.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_id": "<agent_id>"
    },
    "name": "get_linkedin_monitors"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax roster URLs per drill-down page (default 200, capped at 200).
offsetNoRoster rows to skip when paging a monitor_id drill-down (default 0).
agent_idYesThe agent whose monitors to read.
monitor_idNoDrill into one monitor's watched-profile roster by its `id`. Omit for the per-monitor summary of all monitors on the agent.
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: -"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."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
    • 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."
+}
  3. Changed4 schema fields changed
    • addedInput schema / properties / agent_id
      Added value: +{
+  "description": "The agent whose monitors to read.",
+  "type": "integer"
+}
    • changedInput schema / properties / monitor_id / description
      Previous value: -"Drill into one monitor's watched-profile roster by its `id`.\nOmit for the per-monitor summary of all monitors on the task."New value: +"Drill into one monitor's watched-profile roster by its `id`.\nOmit for the per-monitor summary of all monitors on the agent."
    • removedInput schema / properties / task_id
      Removed value: -{
-  "description": "The task whose monitors to read.",
-  "type": "integer"
-}
    • changedInput schema / required
      Previous value: -[
-  "task_id"
-]New value: +[
+  "agent_id"
+]
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint=true, the description discloses that the default response is a summary with only members_count and a 5-URL sample rather than the full roster, why that matters (a list monitor can watch thousands), and that drill-down output is paged with a truncated flag. It also encodes semantics an agent could not infer: run_weekdays uses Mon=0 in the user's timezone, last_run_at is null before the first run, and blank post_filter/engager_icp/engager_instructions mean permissive defaults that must be re-passed when re-arming capture.

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: the purpose and the pre-edit read requirement come first, followed by the default-vs-drill-down behavior, then the return shapes. It is dense and long, and the XML summary/returns tagging adds markup overhead, but nearly every sentence carries operational information the agent needs.

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?

There is no output schema, so the returns block does the work of describing both response shapes (per-monitor list with named keys, and the paged drill-down with monitor_id, members, offset, limit, truncated) plus the empty-list case. For a read-only tool with five documented parameters, 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3, but the description adds real meaning on top: monitor_id selects summary vs. drill-down and its value comes from the id field of a prior summary, and offset/limit define the paging loop rather than mere pagination knobs. The only unaddressed parameter is on_behalf_of, which is explained only in 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 opening sentence states a specific verb and resource (read LinkedIn post monitors configured on an agent) and enumerates the fields returned (mode, schedule, writing instructions, action flags). It also explicitly differentiates itself from the mutating sibling set_up_linkedin_monitoring, so an agent can route between them without opening either 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?

It gives an explicit workflow rule: call this before editing a monitor because set_up_linkedin_monitoring overwrites fields that are not re-passed, and carry forward unchanged values. It also spells out the branch condition between the summary call (omit monitor_id) and the roster drill-down (pass monitor_id), including the paging loop with offset += limit while truncated is set.

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