Skip to main content
Glama
Sign In
phabricator-mcp

phabricator-mcp

by freelancer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

phabricator_paste_edit

Destructive

Edit an existing Phabricator paste by updating its content, title, language, status, projects, subscribers, or adding a comment.

Instructions

Edit an existing Phabricator paste

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_paste_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
titleNoNew title
statusNoStatus: active or archived
commentNoAdd a comment alongside the edit (supports Remarkup)
contentNoNew content
languageNoSyntax highlighting language
addProjectPHIDsNoProject PHIDs to add
objectIdentifierYesPaste PHID or ID (e.g., "P123")
addSubscriberPHIDsNoSubscriber PHIDs to add
removeProjectPHIDsNoProject PHIDs to remove
removeSubscriberPHIDsNoSubscriber PHIDs to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.19

TDQS

C2.9/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 write profile is covered. The description adds no behavioral context beyond that – it doesn't say that supplying 'content' overwrites prior content, that edits may create a revision, whether comment is separate from the change, or what permissions are needed. For a destructive mutation this is a real gap.

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 filler. It is efficient, though the brevity is under-specification rather than deliberate conciseness that trades off against richer detail.

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 mutation tool with 10 parameters and no output schema, one sentence is not enough. The agent gets no information about overwrite semantics, whether omitted fields are preserved, or what the call returns, leaving behavior to be inferred 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%, with all 10 parameters individually documented (including the P123 vs PHID format for objectIdentifier), so the schema carries parameter semantics. The description contributes nothing further, making the baseline 3 appropriate.

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 states a specific verb (Edit) and resource (an existing Phabricator paste), which clearly disambiguates it from siblings like phabricator_paste_create and phabricator_paste_search. It does not explicitly name those siblings, but the verb+resource pairing is unambiguous.

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?

Nothing tells the agent when to reach for this tool versus phabricator_paste_create or phabricator_paste_search, nor what prerequisites exist (e.g. needing a paste identifier). 'Edit an existing paste' implies usage but gives no guidance or exclusions.

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