Skip to main content
Glama

callingly

by com.callingly
OverviewDiscussionsAdmin

Create, edit or duplicate a follow-up sequence

save_sequence

Create a follow-up sequence, update one (its name, steps, after-hours steps and teams), or duplicate one. To edit steps, read them with get_account_setup (sequence_id), change the list and send the whole list back.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoSequence name (max 255). Required for create.
actionYescreate: a new sequence. update: change sequence_id (only the arguments you pass change). duplicate: copy sequence_id as "<name> (copy)", with no teams.
team_idsNoThe complete list of teams that should run this sequence (ids from get_settings). Omit to leave team assignments unchanged. A team taken off is moved to another sequence.
sequence_idNoThe sequence to update or duplicate.
during_stepsNoSteps run while the team is available, in order (the whole list; replaces the current steps). Types: - wait: unit immediately|minutes|hours (value = how many) or days (value days later, until time) or same_day (until time, HH:MM). The first wait is the initial delay: immediately, minutes or hours only. - call: ring the team's reps. ai-call: the team's AI agent calls; optional introMessage / voicemailMessage (max 500, blank = the agent's own) and isVoicemail (null = the agent's setting). - sms: text the lead (body; merge tags like {{lead.first_name}}, {{lead.<custom field slug>}}, {{from.company}}). An sms right before a call is sent before dialing; right after a call, only if the call is not answered.
outside_stepsNoSteps when a lead arrives outside business hours: at most one sms (body) and one ai-call. Pass [] for none.
reschedule_after_hoursNoFor a lead that arrives outside business hours: true = after outside_steps, wait until the team is next available and run during_steps; false = the sequence ends after outside_steps. Defaults to true on create.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only supply destructiveHint=false, so the description carries real weight: it discloses that during_steps/outside_steps are whole-list replacements, that a team removed from team_ids is moved to another sequence, that duplicate produces "<name> (copy)" with no teams, and that update only mutates the arguments passed. These are non-obvious side effects and mutation semantics beyond any structured field.

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?

Two sentences, zero padding, with the three supported actions and the critical edit-steps workflow front-loaded before any detail.

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 7-parameter mutation tool with no output schema and only a single annotation, the description covers actions, step syntax routing, and side effects. Remaining gaps are minor: no auth/permission requirements and no statement of what is returned.

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; the description goes further by tying the editing workflow to sequence_id and describing what the step arrays replace, adding meaning on top of an already thorough 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?

Names a specific verb set (create/update/duplicate) on a specific resource (follow-up sequence), and enumerates the three modes so an agent can distinguish it from siblings like add_to_sequence or update_schedule at a glance.

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 explicit context for the update path: read steps with get_account_setup(sequence_id), modify the list, and send the whole list back. It does not, however, name alternative tools an agent might confuse it with (e.g. add_to_sequence for attaching a lead versus editing the sequence definition).

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

All callingly toolsInspect
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