Sliq

Detach from outreach

detach_from_outreach

id is the attachment's id as shown on that queued message in the queue status read (manage_email_outreach_queue or manage_linkedin_invite_queue, action='status'). The removed file's name and the files still on that message, shaped {'detached': True, 'filename', 'attachments': [{'id', 'filename', 'mime_type', 'size'}]}.

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": {
      "id": "<id>"
    },
    "name": "detach_from_outreach"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	the attachment's `id` from the queue status read.
`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.

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

Changed2 schema fields changedOct 26, 2026

removedInput schema / properties / recipient_email

Removed value: -{
-  "description": "the queued email's recipient.",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "recipient_email",
-  "id"
-]New value: +[
+  "id"
+]

Changed1 schema field changedOct 19, 2026

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

First observedSep 15, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the safety profile is partly covered. The description adds genuine context beyond that: only queued messages are affected, the detached file's name is reported, and the remaining attachments are returned so the agent can see the post-state. It does not say whether the file stays in the attachment library.

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?

The summary is one front-loaded sentence that carries the core action, followed by a short id-source note. The returns block is justified because no output schema exists. No wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description supplies the return shape, and it explains where the required id originates. What remains thin is the permission/scope implication of on_behalf_of and the fate of the detached file, but an agent can call this correctly from what is given.

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 both parameters are already documented and the baseline is 3. The description reinforces the id's provenance from the queue status read but adds nothing about on_behalf_of beyond what the schema says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The summary states a specific verb and resource — 'Remove a file already attached to a queued outreach email or LinkedIn message' — and scopes it to queued messages. It is clearly the inverse of the sibling attach_to_outreach, though it never names that tool explicitly.

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?

It tells the agent exactly where the required id comes from (the queue status read via manage_email_outreach_queue or manage_linkedin_invite_queue with action='status'), which is real prerequisite guidance. It stops short of stating when not to use it, e.g. that files on already-sent messages cannot be detached.

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?