Tulina

apollo_sequence

Manage Apollo sequences (search/create/update/activate/deactivate/archive).

Args by op:

search: name (partial match), per_page, page. BYO key only — this lists the key owner's OWN sequences (names + open/reply rates).
create: name + emailer_schedule_id REQUIRED (get one from apollo_email_schedules — the API refuses creation without it). Optional active (default False — prefer op="activate" once steps/templates are reviewed), label_names, folder_id, max_emails_per_day, emailer_steps (nested step/template definitions — see Apollo docs). BYO key only.
update: sequence_id + any of name, active, emailer_schedule_id, label_names, max_emails_per_day, cc_emails, bcc_emails, emailer_steps (include id per step to MODIFY it, omit to CREATE one). BYO key only.
activate / deactivate: sequence_id. BYO key only.
archive: sequence_id. BYO key only. Supports dry_run=True (no get-by-id exists on this endpoint — the preview cannot show a real diff, just echoes the intended action).

dry_run=True on create/update/activate/deactivate/archive validates but skips the actual API call.

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": {
      "op": "<op>"
    },
    "name": "apollo_sequence"
  }
}

Input Schema

Name	Required	Description
`op`	Yes
`_org`	No	Org (id) de CET APPEL. `oto_list_orgs()`.
`name`	No
`page`	No
`_group`	No	Équipe (id) de CET APPEL, sous son org parente.
`active`	No
`_run_id`	No	OBLIGATOIRE à chaque appel dès `run_start` ou `data_claim_next` : sans lui, l'écriture sur une ligne réservée est refusée. Hérité seulement si le serveur tient un run actif — n'y compte pas.
`dry_run`	No
`_project`	No	Projet (id) de CET APPEL — jeton PRIMAIRE. `oto_project(op='list')`.
`per_page`	No
`_instance`	No	Instance de connecteur PRÉCISE (un credential exact). `oto_instance(op='list')`.
`cc_emails`	No
`folder_id`	No
`bcc_emails`	No
`label_names`	No
`sequence_id`	No
`emailer_steps`	No
`max_emails_per_day`	No
`emailer_schedule_id`	No

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?

With no annotations, the description carries the full burden and does so well: it discloses the BYO-key-only restriction on every op, the active=False default and its implications, the dry_run contract ('validates but skips the actual API call'), the step-id semantics (include id to modify, omit to create), and even the archive preview limitation since no get-by-id endpoint exists. It also hints at the search return shape (names plus open/reply rates).

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?

One summary sentence followed by a tightly scoped per-op bullet list, front-loaded with the op-as-entrypoint model and a closing note on dry_run scope. No filler, and each bullet earns its place by pairing parameters with constraints.

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 19-parameter, six-operation mutation tool with no annotations and no output schema, this covers the essential behavior: prerequisites, defaults, dry-run semantics, and the archive preview caveat. Pagination behavior for search and a fuller description of the search return payload are the main omissions.

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 26%, but the description compensates by mapping nearly every domain parameter to its op: name/per_page/page for search, sequence_id for update/activate/deactivate/archive, and active/label_names/folder_id/max_emails_per_day/emailer_steps/cc_emails/bcc_emails/emailer_schedule_id for create/update. Only the underscore-prefixed context params are left to the schema, and those are self-documented there.

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 opens with a specific verb and resource ('Manage Apollo sequences') and immediately enumerates all six supported operations (search/create/update/activate/deactivate/archive). The per-op breakdown makes it obvious what each operation targets, so an agent can distinguish this tool from siblings like apollo_sequence_contacts.

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 concrete per-operation routing: create needs an emailer_schedule_id sourced from apollo_email_schedules, and it recommends op="activate" after steps/templates are reviewed instead of passing active=True at creation. It does not, however, explain when to reach for this tool versus apollo_sequence_contacts, so sibling-level routing remains implied.

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

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