Relinta

List outreach enrollments

listOutreachEnrollments

Read-onlyIdempotent

List outreach enrollments

Returns both one-lead API enrollments and native campaign enrollments newest first. source distinguishes api and campaign; campaignId links campaign-generated work. Existing one-lead API ids and their detailed event-derived states remain valid. Campaign work uses planned/active/paused/completed/replied/failed/cancelled; paused means initial contact is held by the parent campaign; already-started sequences continue while new leads are paused. There is no individual pause switch. Filter by campaignId, one connected LinkedIn account, one exact public lead identifier, one playbook, one current state, or an inclusive creation-time range. When pagination.hasMore is true, pass pagination.nextCursor back unchanged with the same filters.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "listOutreachEnrollments"
  }
}

Input Schema

Name	Required	Description	Default
`query`	No

Output Schema

Name	Required	Description	Default
`data`	Yes
`headers`	Yes
`httpStatus`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, and the description adds substantial context beyond that: result ordering, source classification, campaign state meanings, paused behavior, the absence of an individual pause switch, and cursor handling. This is rich behavioral disclosure without contradicting 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?

The description is front-loaded with the core list behavior and then layers on state semantics, filtering, and pagination without much wasted wording. It is dense and could be easier to scan with structure, but the length is justified by the tool's complexity.

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?

For a complex filtered-list tool with annotations and an output schema, the description covers the key behavioral and pagination context an agent needs. It leaves a few filter details to the input schema, especially executionStatus and limit, but is otherwise complete enough to invoke 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?

The description names most filter dimensions (campaignId, connected LinkedIn account, exact lead identifier, playbook, current state, inclusive creation-time range) and explains that nextCursor must be reused unchanged with the same filters. It does not mention executionStatus or limit, and the leadId/leadIdType pairing is only implied, so some parameter detail is left 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 description gives a specific verb and resource (list outreach enrollments) and immediately explains the two result families: one-lead API enrollments and native campaign enrollments, newest first. It also names the source and campaignId fields that distinguish them, so an agent can separate this from get/create/cancel enrollment siblings.

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 gives clear operational guidance for filtering by campaign, LinkedIn account, lead identifier, playbook, state, or creation-time range, and explains pagination cursor reuse. It does not explicitly say when to use this list tool versus getOutreachEnrollment for a single enrollment, so it stops short of full alternative routing.

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

All Relinta 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?