Skip to main content
Glama
tasklite-net

TaskLite MCP

by tasklite-net
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_automation

Set up automated board workflows by pairing triggers with actions, such as scheduled HTTP requests that fetch external data and update columns automatically.

Instructions

Create an automation on a board: when something happens, do something. The most useful action here is http_request, which calls an external API and writes the answer back into columns — pair it with the "scheduled" trigger and the board keeps itself up to date (prices, exchange rates, shipment status, weather). Triggers: item_created, status_changed, column_value_changed, date_approaching, scheduled. Actions: http_request, send_notification, send_email, change_status, set_column_value, create_cross_board_item, send_webhook. Two more things every action list can use: a { type: "delay", config: { minutes | hours | days } } action pauses the run and resumes the actions after it later (reminders, follow-ups); and any network action (http_request, send_webhook, send_email, send_whatsapp) may carry config.retry: { attempts (1-5), delaySeconds (1-60) }. send_webhook accepts config.secret for an HMAC signature.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesHuman-readable name
actionsYese.g. [{ type: "http_request", config: { url: "https://api.frankfurter.app/latest?from=USD&to=ILS", method: "GET", responseMapping: [{ path: "rates.ILS", columnId: "<column id from get_board_schema>" }] } }]
boardIdYesBoard id (from list_boards / create_board)
triggerYesEvent that starts the automation: item_created, status_changed, column_value_changed, date_approaching, or scheduled (cron)
isActiveNoWhether it is active
projectIdYesProject id (from list_projects / create_project)
triggerConfigNoe.g. { cron: "0 8 * * *" } for scheduled, { columnName } for column_value_changed

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv0.13.0
    • addedInput schema / properties / actions / items / properties / config / description
      Added value: +"Action-specific config, e.g. { url, method, headers, responseMapping } for http_request"
    • addedInput schema / properties / actions / items / properties / type / description
      Added value: +"Column type: text, rich_text, number, status, date, datetime, duration, people, checkbox, dropdown, label, priority, link, email, phone, relation, lookup, rollup, rating, currency, file"
    • addedInput schema / properties / boardId / description
      Added value: +"Board id (from list_boards / create_board)"
    • addedInput schema / properties / isActive / description
      Added value: +"Whether it is active"
    • addedInput schema / properties / name / description
      Added value: +"Human-readable name"
    • addedInput schema / properties / projectId / description
      Added value: +"Project id (from list_projects / create_project)"
    • addedInput schema / properties / trigger / description
      Added value: +"Event that starts the automation: item_created, status_changed, column_value_changed, date_approaching, or scheduled (cron)"
  2. First observedv0.7.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only state readOnlyHint=false and destructiveHint=false. The description adds meaningful behavioral detail: http_request writes responses back into columns, delay actions pause and resume the run, network actions support retry config, and send_webhook accepts an HMAC secret. No contradiction with annotations.

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?

The description is dense but well organized: it starts with the core purpose, highlights the most useful action pattern, then compactly enumerates triggers, actions, and cross-cutting options like delay and retry. Every sentence contributes useful information without filler.

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 complex tool with 7 parameters, nested objects, and no output schema, the description covers invocation well: all trigger and action categories, common configs, and examples. The main omissions are the return format and when triggerConfig is required, but these are minor relative to the overall completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds essential value beyond the schema by giving concrete examples for the actions array, triggerConfig, delay behavior, retry settings, and webhook secret usage. This is especially important for the complex nested actions parameter.

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-resource pair ('Create an automation on a board') and explains the trigger/action model in plain language. The enumerated triggers and actions clearly identify what the tool does and distinguish it from sibling tools like list_automations or create_board.

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?

The description gives concrete use context, such as pairing the scheduled trigger with http_request to keep a board updated with prices or exchange rates, and lists valid triggers and actions. It does not explicitly say when not to use the tool or name alternatives, but the guidance is clear enough for an agent to select it appropriately.

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

Deploy Server

Other Tools