CRM Connector

Propose: Take out of a workflow

propose_remove_from_workflow

AI Agents (inside one system): Use when the person asks for this in a system whose AI agent may change records: A record taken out of a workflow or campaign, so its next steps do not run for it. Only the person can approve it. Give one item per record, at most 25. Nothing is written yet: the answer shows, per record, what it holds now and would hold after, plus a proposal id. Show it to the person, say so first when something would be sent to the people in their system, ask whether to go ahead, and only then call apply_proposal; when needsApproval is true, share the approve link instead. Not for reading (use search_records or get_record).

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": {
      "system": "<system>",
      "items": "<items>"
    },
    "name": "propose_remove_from_workflow"
  }
}

Input Schema

Name	Required	Description	Default
`items`	Yes	One object per record, at most 25.
`system`	Yes	Which AI agent: the system's id from get_ai_agent_options, or the name of the system or its connection. Ask the person which AI agent they mean unless they named it in this conversation; never pick one yourself.

Output Schema

Name	Required	Description	Default
`notice`	No
`changes`	Yes
`systemId`	Yes
`warnings`	Yes
`expiresAt`	Yes
`approveUrl`	Yes
`proposalId`	Yes
`systemName`	Yes
`needsApproval`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 10, 2026

changedInput schema / properties / items / items / properties / automation_kind / enum

Previous value: -[
-  "workflow",
-  "campaign",
-  "sequence"
-]New value: +[
+  "workflow",
+  "campaign",
+  "sequence",
+  "macro"
+]

changedInput schema / properties / items / items / properties / type / enum

Previous value: -[
-  "contact",
-  "opportunity"
-]New value: +[
+  "contact",
+  "opportunity",
+  "ticket"
+]

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / system / description

Previous value: -"Which AI agent: the system's id from get_ai_agents_info, or the name of the system or its connection. Ask the person which AI agent they mean unless they named it in this conversation; never pick one yourself."New value: +"Which AI agent: the system's id from get_ai_agent_options, or the name of the system or its connection. Ask the person which AI agent they mean unless they named it in this conversation; never pick one yourself."

AddedNov 5, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), it discloses what the call actually does: 'Nothing is written yet,' the answer shows per-record before/after state plus a proposal id, and a proposal must be human-approved. It also warns about an external side effect the annotations only hint at via openWorldHint — surfacing first when something 'would be sent to the people in their system.'

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?

It is information-dense and front-loads the operation before the approval workflow, but the opening 'AI Agents (inside one system): Use when...' preamble is awkward and the final sentence packs four separate instructions into one run-on. The 'one item per record, at most 25' instruction duplicates the schema, which is the only clear waste.

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?

For a proposal-creation tool with an output schema, annotations, and fully documented params, this covers everything an agent needs: when to use it, the per-record unit of work, the human-approval gate, the side-effect warning, and the handoff to apply_proposal. Return values are summarized rather than specified, which is appropriate given the output schema exists.

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 real guidance beyond the schema for the `system` parameter: ask the person which AI agent they mean, never pick one yourself. It restates the 25-item cap, which is redundant with maxItems/minItems, but the conversational constraint on `system` is genuinely new meaning.

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 description names the specific resource and outcome: 'A record taken out of a workflow or campaign, so its next steps do not run for it.' It also separates itself from the reading siblings ('Not for reading (use search_records or get_record)'), so an agent can tell what class of operation this is 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?

It gives an explicit triggering condition ('Use when the person asks for this in a system whose AI agent may change records'), an explicit exclusion with named alternatives (search_records, get_record), and a full escalation path: show the person, ask, then call apply_proposal, or hand over the approve link when needsApproval is true.

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

All CRM Connector 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?