Skip to main content
Glama

phabricator_task_create

Create a new Maniphest task with a title and optional details such as status, priority, owner, description, projects, and subscribers.

Instructions

Create a new Maniphest task

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": {
      "title": "<title>"
    },
    "name": "phabricator_task_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceNoSpace PHID to place the task in (for multi-space installations)
titleYesTask title
pointsNoStory points value (if points are enabled on this instance)
statusNoInitial status
commentNoInitial comment on the task (supports Remarkup)
subtypeNoTask subtype (e.g. "default", "incident")
priorityNoPriority keyword (unbreak, triage, high, normal, low, wish) or numeric value
ownerPHIDNoAssigned owner PHID
commitPHIDsNoCommit PHIDs to associate (for actual commits only, not revisions)
descriptionNoTask description (supports Remarkup)
parentPHIDsNoParent task PHIDs
revisionIDsNoDifferential revision IDs to link (e.g. ["D223125"] or ["PHID-DREV-xxx"]). Creates a bidirectional link between the revision and the task.
customFieldsNoCustom field transactions. Keys are transaction types (e.g. "custom.my-field"), values are the field values. phabricator_task_search with includeEmptyCustomFields: true lists every key.
projectPHIDsNoProject PHIDs to tag
subtaskPHIDsNoSubtask PHIDs
subscriberPHIDsNoSubscriber PHIDs

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.1.0
    • changedInput schema / properties / customFields / description
      Previous value: -"Custom field transactions. Keys are transaction types (e.g. \"custom.my-field\"), values are the field values. Check your Phabricator Conduit console (conduit/method/maniphest.edit/) for available fields."New value: +"Custom field transactions. Keys are transaction types (e.g. \"custom.my-field\"), values are the field values. phabricator_task_search with includeEmptyCustomFields: true lists every key."
  2. First observedv2.0.19

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation profile is covered. The description adds nothing beyond that: no mention of required permissions, rate limits, whether custom fields must be pre-approved, or what the tool returns (task PHID/ID). With 16 parameters and no output schema, this leaves the agent under-informed about a write operation.

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

Conciseness3/5

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

The single sentence is concise but under-specified for a 16-parameter creation tool. It wastes no words but also fails to front-load any useful context, such as required fields or supported features.

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

Completeness2/5

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

For a complex creation tool with 16 parameters, nested customFields, and no output schema, the description omits what is returned, whether partial success is possible, and what environment constraints apply. It is far too thin relative to the tool's complexity.

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%, so all 16 parameters are well documented in the schema itself. The description repeats nothing and adds no additional parameter meaning, making 3 the appropriate baseline when the schema does the heavy lifting.

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?

States a specific verb ('Create') and resource ('Maniphest task'), so an agent immediately knows the operation. However, it does not distinguish itself from siblings such as phabricator_task_edit, which could also modify existing tasks, leaving differentiation implicit.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus phabricator_task_edit or other creation tools. It also omits prerequisites, such as whether the caller needs a space PHID or which fields are mandatory beyond 'title'.

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