Skip to main content
Glama

phabricator_task_edit

Modify an existing Phabricator Maniphest task's title, description, status, priority, owner, projects, subscribers, and associated commits or revisions. Supports custom fields and workboard column moves.

Instructions

Edit an existing Maniphest task

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
objectIdentifierYesTask PHID or ID (e.g., "T123" or PHID)
titleNoNew title
descriptionNoNew description
ownerPHIDNoNew owner PHID (null to unassign)
priorityNoNew priority
statusNoNew status: open, resolved, wontfix, invalid, spite, duplicate
subtypeNoTask subtype (e.g. "default", "incident")
addProjectPHIDsNoProject PHIDs to add
removeProjectPHIDsNoProject PHIDs to remove
addSubscriberPHIDsNoSubscriber PHIDs to add
removeSubscriberPHIDsNoSubscriber PHIDs to remove
addParentPHIDsNoParent task PHIDs to add
removeParentPHIDsNoParent task PHIDs to remove
addSubtaskPHIDsNoSubtask PHIDs to add
removeSubtaskPHIDsNoSubtask PHIDs to remove
addCommitPHIDsNoCommit PHIDs to associate (for actual commits only, not revisions)
removeCommitPHIDsNoCommit PHIDs to disassociate (for actual commits only, not revisions)
addRevisionIDsNoDifferential revision IDs to link (e.g. ["D223125"] or ["PHID-DREV-xxx"]). Creates a bidirectional link between the revision and the task.
removeRevisionIDsNoDifferential revision IDs to unlink (e.g. ["D223125"] or ["PHID-DREV-xxx"]).
pointsNoStory points value (null to clear)
columnPHIDNoMove to workboard column
spaceNoSpace PHID to move the task to (for multi-space installations)
commentNoAdd a comment alongside the edit (supports Remarkup)
customFieldsNoCustom 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.
Behavior2/5

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

No annotations exist, so the description carries full burden. It only states 'Edit an existing Maniphest task', which implies mutation but lacks details on permissions, side effects (e.g., overwriting fields not provided), or response behavior.

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 description is extremely concise (one sentence) but lacks important context for a tool with 24 parameters. While brevity is valued, the content is insufficient, falling between efficient and under-specified.

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?

Given the tool's complexity (24 parameters, no output schema, no annotations), the description is far too minimal. It does not cover return values, error conditions, or partial update behavior, leaving the agent underinformed.

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 baseline is 3. The description adds no additional parameter context beyond the schema; it merely states the tool's action. No added value.

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 'Edit an existing Maniphest task' clearly states the action (edit) and the resource (Maniphest task), distinguishing it from sibling tools like phabricator_task_create and phabricator_task_search.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives, such as when to add a comment vs. edit a task, nor any prerequisites or context for invoking the tool.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/freelancer/phabricator-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server