Skip to main content
Glama
Sign In

Sliq

by com.getsliq
OverviewDiscussionsAdmin

Retry blocked enactment

retry_blocked_enactment

A retry with the cause still in place fails and re-blocks identically — fix the cause in the same call: pass email for an email-shaped block (email_not_found, a missing address) and/or linkedin_slug for a wrong or missing LinkedIn identifier (missing_identifier, a failed resolution). Both fix the EXISTING prospect's person — never re-add the person via track_prospects with the new contact info, which creates a duplicate prospect. On an Instantly step, missing_identifier means the prospect has no stored email address, so pass email for it. A cr_already_sent block has no fix here: Sliq's records show an earlier connection request to this person that is queued, was sent, or failed, and Sliq won't queue a second one while that request stands. Tell the user; if they have since invited them by hand, call register_manual_linkedin_invites, which picks the campaign up from that invite; otherwise drop the prospect with update_prospect(stage='skipped'). A name_mismatch block means the LinkedIn profile belongs to someone other than the person they were added as (data.supplied_name): retrying continues the campaign with that profile — do it only when it's the same person under another name; otherwise skip the prospect and track the intended person (a linkedin_slug fix is refused on this block). An instantly_failed block means the prospect's Instantly handoff failed; the last_error of the last entry in their instantly_handoffs on query_prospects says why. When it says Instantly refused the lead and Instantly's message is about the address, retry with a corrected email. When the lead was moved out of the campaign or is gone from the workspace, someone changed it in Instantly: ask the user whether to hand the prospect off again, then retry, or drop them with update_prospect(stage='skipped'). For any other cause, tell the user what it says and retry once they have fixed it. An instantly_already_in_campaign block means the address was already a lead in that Instantly campaign, which Sliq left as it was: once the user removes that lead in Instantly, retry. An email_unsubscribed block has no fix here: the person unsubscribed from the user's emails in Instantly. Tell the user. If they want the campaign to go on without email, move the prospect past the step with move_prospect_to_node; to stop, drop them with update_prospect(stage='skipped'). Dict confirming the prospect, the node they rest on, the cleared reason, and any contact fixes applied (email / linkedin_slug). An email fix lands on the person's profile, the prospect's only address.

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>",
      "prospect_id": "<prospect_id>"
    },
    "name": "retry_blocked_enactment"
  }
}

Input Schema

NameRequiredDescriptionDefault
emailNoAn address to stamp on the prospect before retrying (optional) — the same write as update_prospect's `email`; refused if another person in the workspace already carries it.
agent_idYesID of the agent whose flow the prospect is on.
prospect_idYesThe prospect's `id` — the outreach_prospects primary key, as returned on every query_prospects row.
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.
linkedin_slugNoA corrected LinkedIn profile slug, or the profile URL (optional). Applied as an unverified claim the retried send verifies through the profile resolver, so a wrong-person pairing is held for adjudication like any other. On a previously-verified profile (a dead or reassigned URL) the old verification is cleared and the corrected identity re-verifies fresh; refused only when a teammate's prospect verified the same person — remove this prospect and track the correct profile instead.

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. Changed2 schema fields changed
    • addedInput schema / properties / linkedin_slug
      Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "A corrected LinkedIn profile slug, or the profile URL (optional). Applied as\nan unverified claim the retried send verifies through the profile\nresolver, so a wrong-person pairing is held for adjudication like any\nother. On a previously-verified profile (a dead or reassigned URL) the\nold verification is cleared and the corrected identity re-verifies\nfresh; refused only when a teammate's prospect verified the same\nperson — remove this prospect and track the correct profile instead."
+}
    • removedInput schema / properties / linkedin_url
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null,
-  "description": "A corrected LinkedIn profile URL or slug (optional). Applied as\nan unverified claim the retried send verifies through the profile\nresolver, so a wrong-person pairing is held for adjudication like any\nother. On a previously-verified profile (a dead or reassigned URL) the\nold verification is cleared and the corrected identity re-verifies\nfresh; refused only when a teammate's prospect verified the same\nperson — remove this prospect and track the correct profile instead."
-}
  3. 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."
+}
  4. Changed1 schema field changed
    • changedInput schema / properties / email / description
      Previous value: -"An address to stamp on the prospect before retrying (optional) — the\nsame write as update_prospect's `email`; refused if another prospect in\nthe account already owns it."New value: +"An address to stamp on the prospect before retrying (optional) — the\nsame write as update_prospect's `email`; refused if another person in the\nworkspace already carries it."
  5. Changed3 schema fields changed
    • addedInput schema / properties / agent_id
      Added value: +{
+  "description": "ID of the agent whose flow the prospect is on.",
+  "type": "integer"
+}
    • removedInput schema / properties / task_id
      Removed value: -{
-  "description": "ID of the task whose flow the prospect is on.",
-  "type": "integer"
-}
    • changedInput schema / required
      Previous value: -[
-  "task_id",
-  "prospect_id"
-]New value: +[
+  "agent_id",
+  "prospect_id"
+]
  6. Changed1 schema field changed
    • changedInput schema / properties / linkedin_url / description
      Previous value: -"A corrected LinkedIn profile URL or slug (optional). Applied as\nan unverified claim the retried send verifies through the profile\nresolver, so a wrong-person pairing is held for adjudication like any\nother. Refused once a live lookup verified the current profile — a\ndifferent URL then means a different person: remove them from the\ncampaign and track the correct profile instead."New value: +"A corrected LinkedIn profile URL or slug (optional). Applied as\nan unverified claim the retried send verifies through the profile\nresolver, so a wrong-person pairing is held for adjudication like any\nother. On a previously-verified profile (a dead or reassigned URL) the\nold verification is cleared and the corrected identity re-verifies\nfresh; refused only when a teammate's prospect verified the same\nperson — remove this prospect and track the correct profile instead."
  7. 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, so the description must carry the behavioral load, and it does: it states the prospect is left 'resting unstamped on their current node' and that the flow mover re-fires the step on its next pass (roughly every 15 minutes, longer if runs are queued). It also explains that an unfixed retry re-blocks identically, and that a linkedin_slug fix is refused on name_mismatch — none of which the annotations convey.

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 core behavior and timing caveat are front-loaded before the per-block-reason reference, which is the right ordering for a long definition. It is nonetheless a very long block of prose with repeated 'Tell the user' constructions and a mid-sentence header collision ('An `instantly_already_in_campaign` block...') that slightly hurt scanability.

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, but the definition embeds a returns section describing the confirmation dict, the node, the cleared reason, and applied fixes. Combined with coverage of every enumerated block cause, the duplicate-creation trap, and the timing model, an agent has everything needed to call this correctly.

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% and the schema itself is unusually detailed, so baseline is 3, but the description adds meaning the schema cannot: which parameter to pass for which block reason (email for email_not_found/missing_identifier/Instantly address refusals, linkedin_slug for missing_identifier, refusal of linkedin_slug on name_mismatch). What it does not add is semantics for on_behalf_of, which is left entirely to 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 gives a specific verb and resource — 'Clear a prospect's blocked flow step so it retries, fixing the blocking contact info in the same call' — and the body names the sibling tools it is not (report_enactment_blocked, query_prospects, move_prospect_to_node, update_prospect). An agent can distinguish it from those siblings without opening any 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 explicit when-to-use guidance ('A blocked prospect, see report_enactment_blocked or `enact_blocked_reason` on query_prospects') and explicit when-not-to guidance with named alternatives for each block class: cr_already_sent routes to register_manual_linkedin_invites or update_prospect(stage='skipped'), email_unsubscribed routes to move_prospect_to_node or 'skipped'. It also warns never to re-add the person via track_prospects.

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