Tools

Five tools. One creates, two read, two edit.

Creating

Creates a project and its ordered stages in one call.

Field	Type	Notes
name	string	Required. The pipeline name.
overview	string	Short description shown on the project.
brief	string	Longer context behind the pipeline.
category	string	Optional label, up to 40 characters.
link	string	Optional external http(s) URL.
owner_email	string	The OneTap user who owns it. Ignored for OAuth callers, who always own what they create.
stages[]	array	Required, 1–25 items. Each takes title (required), description, goal, achievement, priority (low \| medium \| high) and dueDate (YYYY-MM-DD).

The owner is seeded as lead and auto-assigned to every stage. The latest stage dueDate becomes the project deadline.

Lists the caller's pipelines with their id, status, dates and stage count.

Field	Type	Notes
owner_email	string	Optional. Whose pipelines to list, for bearer-token callers.

Returns one pipeline's dates and status, plus every stage's id, title, status, priority and due date.

Field	Type	Notes
pipeline_id	string	Required.

This is how you find a stage_id before editing a stage.

Both editors are partial: only the fields you pass change.

Edits one stage.

Field	Type	Notes
stage_id	string	Required.
due_date	string	YYYY-MM-DD, or an empty string to clear the date.
status	enum	todo \| in_progress \| in_review \| done
priority	enum	low \| medium \| high
title, description, goal, achievement	string	Stage copy fields.

Edits project-level fields.

Field	Type	Notes
pipeline_id	string	Required.
name, overview, category, link	string	Project copy fields.
start_date, end_date	string	YYYY-MM-DD, or an empty string to clear.
status	enum	active \| on_hold \| completed \| archived