Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Generate Monitored Post Comment

generate_monitored_post_comment
Destructive

Prefer this over queue_linkedin_post_engagement (with your own text) when acting on a post from the agent's monitored-posts feed. Pass a row id from query_monitored_posts. Only posts with no queued comment are eligible ('filtered', 'skipped', 'skipped_no_credit', 'captured', 'surfaced'); already-commented, queued, or user-rejected posts are refused. A queued-status dict in one of three forms. {'queued': True, 'awaiting_approval': bool, 'status': 'queued', 'draft_comment': str, 'agent_id': int, 'message': str} on success (1 credit charged); agent_id is the agent monitoring the post {'queued': False, 'deduped': True, 'message': str} if a comment is already queued {'queued': False, 'error': 'not_found'|'not_eligible'|'out_of_credits'|'no_draft'} otherwise

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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.
monitored_post_idYesThe `id` of a monitored_posts row (from query_monitored_posts).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / on_behalf_of / description
      Previous value: -"Draft on a consented teammate's monitored post instead of your\nown — pass their email; the 1-credit charge lands on their account. Gated\non that teammate's act-on-behalf setting; a teammate who hasn't granted it\nis 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 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": "Draft on a consented teammate's monitored post instead of your\nown — pass their email; the 1-credit charge lands on their account. Gated\non that teammate's act-on-behalf setting; a teammate who hasn't granted it\nis rejected. Omit for your own."
-}
    • addedInput schema / properties / on_behalf_of
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Draft on a consented teammate's monitored post instead of your\nown — pass their email; the 1-credit charge lands on their account. Gated\non that teammate's act-on-behalf setting; a teammate who hasn't granted it\nis 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. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: 1-credit charge, feed status flip to 'queued', dedupe behavior, refusal cases, and detailed return/error forms. These disclosures are critical for a destructive, credit-consuming mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core action and then provides eligibility and return details in a structured summary/returns format. The length is justified by the mutation, credit charge, and multiple result states.

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?

Given no output schema, the description supplies detailed return shapes and error states. Combined with eligibility rules, cost, and side effects, it is complete enough for an agent to call and interpret results correctly.

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 the schema already documents both parameters. The description reinforces that monitored_post_id comes from query_monitored_posts but adds little parameter-level meaning beyond the schema, and it does not elaborate on on_behalf_of.

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 and resource: draft and queue a comment for one monitored post. It also distinguishes the tool from queue_linkedin_post_engagement and identifies the feed/source context, so an agent can select it 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?

Gives explicit when-to-use guidance, names the preferred alternative, explains the source of monitored_post_id, and lists eligible versus refused post states. This is enough to decide use versus non-use.

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