Jaggle

Add one plain-text comment using Jaggle's Project Commenter permission.

Make one same-project task block or constrain another. predecessor_task_id is the blocker and successor_task_id is the task waiting on it. FS is the normal "successor waits until predecessor finishes" relation; SS, FF, and SF express start/finish scheduling constraints. Jaggle checks permissions, endpoint scope, duplicate edges, and cycles.

Add an existing workspace member to a team after Team Admin checks.

Append escaped plain text to a pageless BlockNote project document.

Approve a task only as its assigned approver under Project Editor checks.

Archive one task after exact confirmation and Project Editor enforcement.

Add an active workspace member as a task assignee with Project Editor checks.

Set one typed custom field value on 1-25 tasks in the same authorized project.

Move a task to a status board within the same explicit project and workspace.

Disable and clear a form's task destination and assignee mapping.

Clear one hub child field value after exact confirmation and scope checks.

Clear one task field value after exact confirmation and relationship checks.

Map submissions to tasks on one verified board and project-member assignee.

Configure manual or automatic goal tracking with validated source combinations.

Create a project automation draft under Project Admin and plan checks. Resolve node types/config fields with get_automation_catalog. Incoming pipelines use if.webhook_received with an endpoint_id; outgoing requests use an action.send_webhook node with an HTTPS url and POST, PUT, or PATCH method. Task-description templates must be BlockNote-compatible semantic HTML.

Create the next immutable incoming payload contract version. Preview the same contract and a realistic sample before activating it. Mapped values become webhook.<key>; redacted or sensitive pointers cannot be mapped.

Create an incoming endpoint and return its secret exactly once. Store the returned secret securely and configure the sender to use X-Jaggle-Webhook-Secret. Do not place it in query parameters or workflow text.

Create one project board/status under Project Editor permission. Omit index to append after the last board. Jaggle currently defines no separate subscription entitlement for project boards.

Create a named checklist group for one permission-checked task.

Create a full task linked beneath a visible parent task.

Create a starter blank, BPMN, workflow, ERD, flowchart, mind-map, or org-chart diagram.

Create one permission- and subscription-checked goal. Manual goals default to percentage tracking. Automatic goals may use projects, tasks, or sub-goals with a compatible measurement type. Project sources and an optional same-workspace parent are validated before creation. The caller becomes Goal Admin. Add members, teams, task sources, and custom weights with the dedicated tools after creation.

Create one hub after workspace permission and subscription checks. The caller becomes Hub Admin. An optional parent hub must be accessible and belong to the same workspace. Add projects, members, and teams with their dedicated tools after creation.

Create a typed custom field owned by one authorized, plan-enabled hub. The backend requires Hub Editor or Admin access. Initial options are accepted only for single_select and multi_select fields.

Create an explicitly scoped Insights dashboard after subscription checks.

Create one private project after explicit confirmation and backend permission checks. The connected user must be an accepted workspace member with Jaggle's create/projects permission. The caller becomes Project Admin. Templates, members, teams, hubs, custom modules, and public visibility are intentionally unsupported. Never retry automatically after a timeout.

Create a typed custom field attached to one explicitly authorized project. Field-type configuration is validated by Jaggle. Initial options are accepted only for single_select and multi_select fields.

Create a complete custom, BPMN, ERD, workflow, flowchart, mind-map, or org-chart diagram.

Create a pageless document with fixed BlockNote editor metadata.

Create a project form after Forms-module, role, and plan-limit checks.

Create a saved project task view with filters, sorting, and grouping. By default the tool clones the project's system view matching view_type. Set source_view_id to clone another same-type view, including its layout, then merge the supplied configuration. Resolve status, assignee, and custom field IDs with the read tools before asking the user to confirm.

Create a lightweight subtask/todo under one permission-checked project task.

Create one task after explicit confirmation and Project Editor enforcement. The board/status must belong to the explicitly supplied project and workspace. Assignees, teams, labels, subtasks, custom fields, dependencies, completion, favourites, ranking overrides, and bulk creation are intentionally unsupported. description is BlockNote-compatible semantic HTML: use paragraphs and wrap list item content in <p>; never send Markdown or BlockNote JSON. Never retry automatically after a timeout.

Atomically create between 1 and 25 bounded tasks on one authorized board. Every supplied task description must be BlockNote-compatible semantic HTML.

Create a workspace team and make the caller its Team Admin.

Create a todo, optionally inside a checklist group, under a task.

Soft-delete an automation after exact confirmation.

Delete an incoming webhook endpoint after exact confirmation.

Delete a board and move every task to a different same-project board. Resolve both IDs with list_project_statuses and show the board names, source task count, destination, and approval-protection state before confirmation. MCP always supplies target_board_id so Jaggle never implicitly deletes tasks.

Delete one verified diagram edge after exact confirmation.