Skip to main content
Glama

tasks_create

Create a task in this workspace. Leave the assignee empty to put it in the backlog, or name someone to hand it over.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesTask title
due_atNoISO datetime when the task is due, e.g. '2026-03-31T15:00:00Z'. A time without a zone is read as UTC.
tag_idsNoTopics for the task: ids of workspace tags that apply to tasks (ai_tags.list with applies_to='task'). Replaces the current set; [] clears it.
agent_idNoAct as this agent instead of as yourself — the task is recorded as authored by it. Optional.
assigneeNoWho should do this: a workspace member (email, username, or user:<id> as workspace.members lists them), an AI agent (its name), or a contact (display name). Use 'me' for yourself. Call workspace.members to see who can be assigned. Where this listing offers assignee_user_id / assignee_agent_id / assigned_to_contact_id, they name an exact target instead.
due_dateNoDate when task is due (e.g. '2026-03-31'). Use with due_time or alone.
due_timeNoTime when task is due (e.g. '15:00'). Used with due_date.
priorityNoTask priority (default: medium)
thread_idNoRelated thread ID
descriptionNoDetailed description
repeat_unitNoUnit for repeat_every.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.
repeat_everyNoMake the task repeat: completing it creates the next occurrence, due this many repeat_unit after the previous deadline. E.g. repeat_every=3, repeat_unit='month' for quarterly.
target_sessionNoWhich desktop Claude session should run this, by the name shown in workspace.desktops. Only needed when the assignee is an AI agent that runs on a machine and more than one session is connected — otherwise the task is not dispatched at all, rather than sent to a machine you did not mean.
assignee_user_idNoExact workspace member to assign to
assignee_agent_idNoExact AI agent to assign to
attachment_file_idsNoFile IDs to attach (from files.upload)
assigned_to_contact_idNoExact contact to assign to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / assignee / description
      Previous value: -"Who should do this: a workspace member (email or username), an AI agent (its name), or a contact (display name). Use 'me' for yourself. Call workspace.members to see who can be assigned. For an exact target, pass assignee_user_id / assignee_agent_id / assigned_to_contact_id instead."New value: +"Who should do this: a workspace member (email, username, or user:<id> as workspace.members lists them), an AI agent (its name), or a contact (display name). Use 'me' for yourself. Call workspace.members to see who can be assigned. Where this listing offers assignee_user_id / assignee_agent_id / assigned_to_contact_id, they name an exact target instead."
  2. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
      +  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
      +  "type": "integer"
      +}
  3. Added
  4. Removed
  5. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.