Skip to main content
Glama

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Set Linkedin Warmup

set_linkedin_warmup

disabled=True opts out of the ramp (full daily volume right away — only safe on an already-warm account); disabled=False re-enables it (resumes any active ramp). Owner-only. Returns {success, warmup_disabled, is_ramping_up}, the recomputed ramp state. Dict with success, warmup_disabled, and is_ramping_up.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
disabledYesTrue to skip warmup (full volume now), False to re-enable the ramp.
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. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With annotations only declaring readOnlyHint=false and destructiveHint=false, the description adds substantial context: it warns that disabled=True is 'only safe on an already-warm account', notes the call is 'Owner-only' (an auth constraint not in annotations), and describes the recomputed ramp state returned. This is real behavioral disclosure beyond the structured fields.

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 polarity mapping followed by the safety constraint, in a tight summary block with a separate returns section. Every sentence carries load, including the anti-pattern warning about describing the UI instead of acting.

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?

No output schema exists, yet the description spells out the return shape ({success, warmup_disabled, is_ramping_up}) and the auth requirement (owner-only). For a two-parameter mutation with full schema coverage, 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 coverage is 100%, so the baseline is 3, but the description adds a safety caveat the schema omits ('full daily volume right away — only safe on an already-warm account') and clarifies that disabled=False 'resumes any active ramp'. It does not expand on on_behalf_of, which the schema already documents fully.

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+resource ('Turn the new-account warmup ramp off or on for the user's LinkedIn account') and immediately maps the polarity. No sibling tool touches warmup ramp state, and the closest neighbor (set_linkedin_daily_limits) is clearly distinct, so an agent can select it without ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names the triggering conditions ('when the user asks to skip/disable warmup ... or to re-enable it') and adds an execution directive ('actually make the change, don't just describe the UI'). It covers both direction cases but names no exclusion or alternative tool, keeping it at 4 rather than 5.

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