phabricator-mcp

phabricator_document_create

Create a new Phriction wiki document with a slug, title, and Remarkup content using phriction.create, so AI assistants can add wiki pages to Phabricator.

Instructions

Create a new Phriction wiki document. Uses phriction.create (the only method that can create documents).

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": {
      "slug": "<slug>",
      "title": "<title>",
      "content": "<content>"
    },
    "name": "phabricator_document_create"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	Document slug/path (e.g., "projects/myproject/")
`title`	Yes	Document title
`content`	Yes	Document content (Remarkup)
`description`	No	Edit description/summary

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.19May 29, 2026

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 and destructiveHint=false, so the mutation/non-destructive profile is covered. The description adds only the implementation note about phriction.create being the sole creation method — it does not say what happens on a duplicate slug (overwrite, error, new version), whether permissions are required, or what the call returns. Some added value, but the mutation semantics an agent most needs are absent.

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?

Two short sentences, front-loaded with the core action and zero padding. The second sentence is marginally expendable implementation trivia, which keeps it from a 5.

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 create mutation with no output schema, the description should address at minimum duplicate-slug behavior and whether the created document's identifier is returned. Annotations cover the safety profile and the schema covers all four parameters, but these behavioral gaps remain.

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 slug, title, content, and description all documented inline, so the baseline of 3 applies. The description adds no extra meaning — no guidance on slug format expectations, uniqueness, or Remarkup behavior beyond what the schema already states.

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 and resource: "Create a new Phriction wiki document." This clearly separates it from phabricator_document_search, phabricator_document_edit, and phabricator_document_add_comment, though it never names those siblings explicitly. The reference to phriction.create reinforces the operation but is implementation detail rather than purpose.

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?

Creation intent is implied clearly, but the description never states when to use this versus phabricator_document_edit or phabricator_document_search, nor any precondition (does the slug need to be unique, does the wiki space exist?). Nothing is misleading, but routing between create/edit is left to inference.

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

Deploy Server