phabricator-mcp

phabricator_task_edit

Destructive

Edit an existing Maniphest task

Instructions

Edit an existing 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": {
      "objectIdentifier": "<objectIdentifier>"
    },
    "name": "phabricator_task_edit"
  }
}

Input Schema

Name	Required	Description
`space`	No	Space PHID to move the task to (for multi-space installations)
`title`	No	New title
`points`	No	Story points value (null to clear)
`status`	No	New status: open, resolved, wontfix, invalid, spite, duplicate
`comment`	No	Add a comment alongside the edit (supports Remarkup)
`dueDate`	No	Due date (the task's Deadline): "YYYY-MM-DD", read as the start of that day in your Phabricator timezone as the web form sets it; null removes it. Use the date form: an epoch in seconds is accepted only to copy one back from maniphest:deadline.epoch, since a computed epoch is easily a day out in another timezone. Always send the full year; if the user gave none, say which year you used. Phabricator posts a reminder on the task a day before. Shown by phabricator_task_search as maniphest:deadline.
`subtype`	No	Task subtype (e.g. "default", "incident")
`priority`	No	New priority
`ownerPHID`	No	New owner PHID (null to unassign)
`columnPHID`	No	Move to workboard column
`description`	No	New description
`customFields`	No	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.
`addCommitPHIDs`	No	Commit PHIDs to associate (for actual commits only, not revisions)
`addParentPHIDs`	No	Parent task PHIDs to add
`addRevisionIDs`	No	Differential revision IDs to link (e.g. ["D223125"] or ["PHID-DREV-xxx"]). Creates a bidirectional link between the revision and the task.
`addProjectPHIDs`	No	Project PHIDs to add
`addSubtaskPHIDs`	No	Subtask PHIDs to add
`objectIdentifier`	Yes	Task PHID or ID (e.g., "T123" or PHID)
`removeCommitPHIDs`	No	Commit PHIDs to disassociate (for actual commits only, not revisions)
`removeParentPHIDs`	No	Parent task PHIDs to remove
`removeRevisionIDs`	No	Differential revision IDs to unlink (e.g. ["D223125"] or ["PHID-DREV-xxx"]).
`addSubscriberPHIDs`	No	Subscriber PHIDs to add
`removeProjectPHIDs`	No	Project PHIDs to remove
`removeSubtaskPHIDs`	No	Subtask PHIDs to remove
`removeSubscriberPHIDs`	No	Subscriber PHIDs to remove

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv2.5.0Nov 9, 2026

addedInput schema / properties / dueDate

Added value: +{
+  "anyOf": [
+    {
+      "anyOf": [
+        {
+          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+          "type": "string"
+        },
+        {
+          "exclusiveMinimum": 0,
+          "type": "integer"
+        }
+      ]
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "description": "Due date (the task's Deadline): \"YYYY-MM-DD\", read as the start of that day in your Phabricator timezone as the web form sets it; null removes it. Use the date form: an epoch in seconds is accepted only to copy one back from maniphest:deadline.epoch, since a computed epoch is easily a day out in another timezone. Always send the full year; if the user gave none, say which year you used. Phabricator posts a reminder on the task a day before. Shown by phabricator_task_search as maniphest:deadline."
+}

Changed1 schema field changedv2.1.0Oct 22, 2026

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."

First observedv2.0.19May 29, 2026

TDQS

C2.6/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is carried by structured data. The description adds no behavioral context at all: it does not say that unlisted fields are left untouched, that null clears points/owner/dueDate, that remove* parameters delete associations, or that the edit is recorded as a transaction. For a 25-parameter destructive mutation, that is a substantial gap even against a lower bar.

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?

A single front-loaded sentence with no padding or throat-clearing; nothing in it is wasteful. It is efficient but thin, so it does not reach the top of the scale.

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 destructive, 25-parameter, nested-object mutation with no output schema, the one-line description is not sufficient on its own: it leaves unclear whether unspecified fields are preserved, what happens to cleared values, and whether a transaction or new task version is produced. The schema rescues parameter-level meaning, but the description does not cover 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% and the per-property documentation is unusually rich (dueDate timezone semantics, subtype examples, customFields key format, bidirectional revision linking). The description contributes nothing beyond the schema, so the baseline of 3 applies rather than a penalty.

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

Purpose3/5

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

"Edit an existing Maniphest task" gives a recognizable verb and resource, so the agent knows this mutates a Maniphest task rather than creating or reading one. But it stops there: with 25 parameters spanning status, owner, workboard column, links, subscribers, and custom fields, the description signals none of that surface, and it does not differentiate itself from siblings like phabricator_task_create or phabricator_task_add_comment.

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?

There is no when-to-use guidance and no named alternative. An agent must infer that phabricator_task_add_comment is preferable for a pure comment, or that phabricator_revision_edit exists for the revision side, purely from sibling names rather than from anything stated here.

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

Deploy Server