Sliq

Queue instantly handoffs

queue_instantly_handoffs

A prospect no longer waiting on the step, already handed off on it, or removed from the campaign is skipped. A prospect whose address bounced or was unsubscribed from the user's emails, or who has no stored address, is blocked on the step instead. A dict with queued, one entry per handed-off prospect with its prospect_id and status ('pending_approval' while it waits on the user, else 'pending'), and skipped and blocked, one entry per prospect left out with its prospect_id and reason.

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>",
      "node_id": "<node_id>",
      "prospect_ids": "<prospect_ids>"
    },
    "name": "queue_instantly_handoffs"
  }
}

Input Schema

Name	Required	Description
`node_id`	Yes	The Instantly step's node id.
`agent_id`	Yes	ID of the agent (campaign) whose flow has the Instantly step.
`on_behalf_of`	No	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.
`prospect_ids`	Yes	The prospects to hand off, by `id` — the outreach_prospects primary key, as returned on every query_prospects row and shown on a flow roster line.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 6, 2026

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."

AddedOct 29, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare a non-destructive write; the description goes well beyond them with the approval gating rules (existing Sliq outreach, teammate tracking/contact, off-platform email), the timing expectation ('within minutes'), the paused-campaign caveat, and the distinct skipped-versus-blocked semantics. These are exactly the behavioral facts an agent needs before triggering an irreversible handoff.

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-first then returns structure is well front-loaded and nearly every clause carries information (gating conditions, skip/block branches, output shape). The first sentence is a dense run-on with stacked clauses that would read faster as a short list of trigger conditions.

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?

Although there is no output schema, the embedded returns block documents the queued/skipped/blocked dicts and their status and reason values. Combined with the approval, timing, and pause caveats, an agent has everything needed to call this correctly and interpret the result.

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%, including the on_behalf_of agency/teammate scoping and the prospect_ids primary-key note, so the schema already carries parameter meaning. The description adds no parameter-level detail beyond the concept — nothing about bulk behavior, duplicates, or how node_id and agent_id must stay consistent.

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 — handing prospects resting on a campaign flow's Instantly step into that step's Instantly campaign, one handoff each. The 'resting on the step' qualifier makes the scope narrower than generic movement tools like move_prospect_to_node or attach_to_outreach, so an agent can tell them 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 Guidelines4/5

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

The precondition for use (prospects waiting on an Instantly step) is stated clearly, along with what is deliberately skipped or blocked, which effectively rules out several wrong cases. It stops short of naming explicit alternatives — e.g. move_prospect_to_node or manual queue_email_outreach — so the agent must infer when another tool is the better route.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Sliq tools Inspect

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

Need Help?