Skip to main content
Glama

Add prospects to a sequence

enrollInSequence
Destructive

Add prospects (ids from listProspects) to one of your sequences (id from listSequences). This SENDS REAL MESSAGES from the sequence sender's own inbox and LinkedIn on the sequence's schedule.

Anyone on the do-not-contact list or already in the sequence is skipped, and so is anyone without a revealed email when the sequence has email steps; the result says who was skipped and why.

Tell the user the sequence, who will be added and that messages go out on its schedule, and get an explicit yes before calling.

Clera privately records this tool's inputs and results for usage tracking and support.

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": {
      "sequenceId": "<sequenceId>",
      "prospectIds": "<prospectIds>"
    },
    "name": "enrollInSequence"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdNoOrganization to act as. Only needed when you belong to more than one organization.
sequenceIdYes
prospectIdsYes

Output Schema

NameRequiredDescriptionDefault
messageYes
skippedYes
enrolledYes

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare destructiveHint and openWorldHint true, but the description adds the concrete consequence: real messages are sent from the sender's own inbox and LinkedIn on the sequence's schedule. It further discloses skip logic (do-not-contact, already enrolled, no revealed email with email steps), that the result reports who was skipped and why, the required user consent, and a privacy/data-recording note. This is substantial context beyond the annotations.

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?

Front-loaded with the highest-stakes fact (real messages are sent) in caps, followed by skip rules, consent requirement, and disclosure. Four short paragraphs, each carrying distinct information; the consent restatement is slightly redundant with the send warning but still earns its place as an action gate.

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?

Given an output schema exists, the description needn't enumerate return fields, and it still tells the agent the result reports skips and reasons. Together with the orgId guidance in the schema, an agent has everything needed to call this correctly and safely.

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 description coverage is only 33% (only orgId is documented), so the description must compensate, and it does by explaining that prospectIds come from listProspects and sequenceId from listSequences. It does not describe the 500-item batch limit, whether ids are per-organization, or how partial failures across a batch are represented, leaving some semantics to the schema and output.

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 (add) and resource (prospects into a sequence), names the sibling tools that supply the ids (listProspects, listSequences), and immediately flags that this sends real messages. An agent can distinguish this from read-only siblings like listProspects 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 Guidelines4/5

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

Gives a clear precondition workflow: tell the user the sequence, who will be added, and that messages go out on its schedule, then get an explicit yes before calling. It also explains skip conditions. It stops short of naming an alternative path (e.g., drafting instead of enrolling), so it is strong but not a full when/when-not routing guide.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources