Skip to main content
Glama

tasks_create

Create a task in a project. Tasks are per-project tickets — useful for bugs, todos, or end-user-filed feedback inside your app. Tasks live in the project's own database.

Example:

{
  "project_id": "my-saas",
  "title": "Fix login redirect",
  "description": "After OAuth, users land on /home instead of /dashboard.",
  "priority": "high",
  "labels": ["bug", "auth"]
}

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "title": "<title>"
    },
    "name": "tasks_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoOptional subsystem tag (free-form, e.g. "billing", "auth", "ui") for filtering related tasks.
typeNoDefaults to task. Type is a filter; custom labels are supported. vision — why the organization exists. philosophy — a belief guiding trade-offs, including why it matters. directive — a rule or instruction, including what it supersedes. decision — a steer from the person who owns the project: their words, what it changes, what it replaces, the work it governs. sop — how to carry out a recurring job. spec — what to build and its acceptance criteria. roadmap — direction and outcomes for work ahead. epic — a larger outcome grouping related tasks. task — a concrete piece of current work. bug — behavior that needs correction. report — an observation, incident or customer finding. principle — a reusable rule for making decisions. learning — a lesson supported by experience or evidence. supplier — facts about an external service or supplier. content — a draft or plan for published material. policy — a standing rule governing operations. stance — a position on a subject and its reasoning. When the person who owns the project changes direction, parks or picks something, or overrules a plan, record it as a decision the same day, quoting them.
titleYesShort summary, required.
due_atNoOptional Unix timestamp (ms).
labelsNoTag labels for filtering. The board recognizes explicit opt-ins requires-deployment, requires-smoke-test, and requires-resolution-note as completion guidance. In v1 only requires-deployment has machine-verifiable evidence and blocks close; freeform prose never activates a gate.
statusNoWork records only. Defaults to 'open'. 'backlog' represents untriaged ideas, 'blocked' represents work awaiting external action, and 'needs_review' represents completed work awaiting sign-off.
assigneeNoFree-form assignee (user ID, email, or label).
priorityNoDefaults to 'normal'.
reporterNoOptional reporter override; defaults to the caller.
templateNoOptional template that fills priority, labels, area, and description with defaults. Caller-provided fields override template defaults; `tasks_templates` exposes each template.
parent_idNoOptional parent task ID — makes this a sub-task of the given task.
project_idYesProject ID (UUID), subdomain, or slug, resolved server-side; 'default' is the organization's shared task board.
waiting_onNoExplicit dependency on input or action; explain what is needed in status_note.
attachmentsNosw.fs paths to attach to this task (screenshots, logs, repro files). Each path is a string like "/uploads/screenshot.png" — not a full URL. Max 25 per task.
descriptionNoLong-form body.
status_noteNoOne plain sentence: what is done, next, and blocked. Shown in compact board reads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, so the mutation profile is known. The description adds useful context that records are scoped to the project's own database, but says nothing about duplicate handling, what the call returns (e.g. created task ID), or how template defaults interact with caller fields — all of which matter for a non-idempotent create.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three front-loaded sentences state purpose, use cases, and storage before the example, with no filler prose. The code block is bulky given the schema already enumerates every field, though it does illustrate a realistic composite call, so it only mildly dilutes conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 16-parameter mutation tool with no output schema, the description covers what a task is and where it lives but omits the most confusing aspect: the type parameter defaults to 'task' yet the schema enumerates many other record kinds. It also omits return behavior and template-default precedence, leaving the agent to infer from the schema alone.

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

Parameters3/5

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

Schema description coverage is 100% across 16 parameters, so the schema already carries the semantic load and the baseline is 3. The embedded JSON example usefully demonstrates realistic values for project_id, title, description, priority, and labels, but it adds no meaning beyond those fields and ignores the consequential type, template, status, waiting_on, and parent_id parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource, 'Create a task in a project', and clarifies the domain ('per-project tickets — bugs, todos, end-user-filed feedback') and data locality ('project's own database'). It does not name or distinguish itself from read/update siblings such as tasks_get, tasks_list, or tasks_update, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied via the examples of what tasks are good for (bugs, todos, feedback), which gives some sense of when to reach for this tool. There is no explicit when-not guidance, no mention of when to use tasks_update or a template-driven flow instead, and no prerequisites or permission notes.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources