get_dynamic_sequences - Kalent API

Read-only MCP tool that returns paginated sequence blueprints attached to a sourcing in the authenticated workspace. Use this before start_dynamic_sequences when you need to discover which blueprintId to start.

Input

Parameter	Type	Required	Description
`sourcingId`	string	yes	Sourcing id
`page`	integer	no	Zero-based page index (default `0`)
`pageSize`	integer	no	Page size, max `50` (default `20`)
`search`	string	no	Case-insensitive filter on blueprint name

Output

JSON with:

sequenceBlueprints — blueprintId, name, sourcingId, createdAt, updatedAt, steps, stepCount, channels
pagination — page, pageSize, total, hasNextPage

Returned steps do not expose internal workspaceId or userId fields.

config.userId is never returned, even when a LinkedIn InMail sender is set on the step. A missing userId does not mean the InMail sender is missing: do not invent one. Do not send the returned steps back to update_sequence_blueprint as-is, because that would erase the InMail sender stored on the blueprint.

Example flow

create_sourcing
add_talent_to_sourcing
get_dynamic_sequences with sourcingId
start_dynamic_sequences with blueprintId from the list

See also start_dynamic_sequences and create_sequence_blueprint.