Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Edit Monitor Members

edit_monitor_members

add and remove are LinkedIn profile URLs or vanity slugs for people, and full linkedin.com/company/... URLs for company pages (a bare company name or slug is read as a person's slug). A swap is one call (add=[new], remove=[old]). Both forms of one profile (full URL and bare slug) collapse to a single watched member, so re-adding someone already watched is a no-op. The change takes effect on the monitor's next scheduled run.

Use this instead of re-running setup_linkedin_monitoring whenever the user just wants to tweak who's watched ("also watch Bob", "drop Alice"): setup would force re-passing every existing member, and since each watched profile is billed per run, one dropped URL on the re-echo silently stops watching that person. To change schedule, voice, or the action flags, use setup_linkedin_monitoring (members are preserved there when omitted); adding the very first members or resetting the whole list is setup too. Dict with status ('active'), name, members_count, added, removed, unresolved, and message.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addNoLinkedIn profile URLs/slugs or company page URLs to start watching.
nameYesthe monitor to edit (must already exist on this agent).
removeNoLinkedIn profile URLs/slugs or company page URLs to stop watching.
agent_idYesThe agent the monitor lives on.
on_behalf_ofNoA teammate's email (one with team actions 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: -"Edit a consented teammate's monitor instead of your own — pass\ntheir email; agent_id must be one of their agents. Gated on that teammate's\nact-on-behalf setting; a teammate who hasn't granted it is rejected. Omit\nfor 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 team actions 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": "Edit a consented teammate's monitor instead of your own — pass\ntheir email; agent_id must be one of their agents. Gated on that teammate's\nact-on-behalf setting; a teammate who hasn't granted it is rejected. Omit\nfor your own."
-}
    • addedInput schema / properties / on_behalf_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Edit a consented teammate's monitor instead of your own — pass\ntheir email; agent_id must be one of their agents. Gated on that teammate's\nact-on-behalf setting; a teammate who hasn't granted it is rejected. Omit\nfor 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
    • changedInput schema / properties / add / description
      Previous value: -"LinkedIn profile URLs/slugs to start watching."New value: +"LinkedIn profile URLs/slugs or company page URLs to start watching."
    • changedInput schema / properties / remove / description
      Previous value: -"LinkedIn profile URLs/slugs to stop watching."New value: +"LinkedIn profile URLs/slugs or company page URLs to stop watching."
  4. Changed5 schema fields changed
    • addedInput schema / properties / agent_id
      Added value: +{
+  "description": "The agent the monitor lives on.",
+  "type": "integer"
+}
    • changedInput schema / properties / as_teammate / description
      Previous value: -"Edit a consented teammate's monitor instead of your own — pass\ntheir email; task_id must be one of their tasks. Gated on that teammate's\nact-on-behalf setting; a teammate who hasn't granted it is rejected. Omit\nfor your own."New value: +"Edit a consented teammate's monitor instead of your own — pass\ntheir email; agent_id must be one of their agents. Gated on that teammate's\nact-on-behalf setting; a teammate who hasn't granted it is rejected. Omit\nfor your own."
    • changedInput schema / properties / name / description
      Previous value: -"the monitor to edit (must already exist on this task)."New value: +"the monitor to edit (must already exist on this agent)."
    • removedInput schema / properties / task_id
      Removed value: -{
-  "description": "The task the monitor lives on.",
-  "type": "integer"
-}
    • changedInput schema / required
      Previous value: -[
-  "task_id",
-  "name"
-]New value: +[
+  "agent_id",
+  "name"
+]
  5. 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=false and destructiveHint=false; the description adds substantial context beyond that: incremental semantics, one-call swap, both URL and slug collapse to a single member so re-adding is a no-op, and the change takes effect on the next scheduled run. It also discloses the per-run billing consequence of mishandling members, which is not derivable from annotations.

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-loads the core operation before the alternatives and the returns block, and every section earns its place. It is on the verbose side with narrative asides (the billing warning), but that content is load-bearing rather than filler.

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 a mutation tool with annotations covering the safety profile and a described return shape (status, name, members_count, added, removed, unresolved, message), nothing an agent needs to call it correctly is missing. On-behalf-of behavior is also documented in the schema.

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 lacks: add/remove accept person URLs or vanity slugs and full company URLs, a bare company name is read as a person slug, and swapping is a single call (add=[new], remove=[old]). This is real semantic value beyond the field descriptions.

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 specific verb pair (add and/or remove) and resource (watched people or company pages on an existing list-mode LinkedIn monitor) and explicitly scopes it as incremental. It distinguishes itself from setup_linkedin_monitoring by name, so the agent can tell the two apart 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 explicit when-to-use ('tweak who's watched: also watch Bob, drop Alice') versus when to use the alternative setup_linkedin_monitoring (change schedule, voice, action flags, add the very first members, or reset the whole list). It even explains why setup is dangerous to reuse here (a dropped URL silently stops watching someone).

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