phabricator-mcp

phabricator_blog_post_create

Create a new Phame blog post with a title, body, and target blog; optionally set subtitle, visibility status, and subscribers.

Instructions

Create a new Phame blog post

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>",
      "body": "<body>",
      "blogPHID": "<blogPHID>"
    },
    "name": "phabricator_blog_post_create"
  }
}

Input Schema

Name	Required	Description
`body`	Yes	Post body content (supports Remarkup)
`title`	Yes	Post title
`blogPHID`	Yes	PHID of the blog to post to
`subtitle`	No	Post subtitle
`visibility`	No	Visibility: 0 (draft, default), 1 (published), 2 (archived)
`addSubscriberPHIDs`	No	Subscriber PHIDs to add

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.19May 29, 2026

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=false, so the write/non-destructive nature is covered. The description adds no behavioral context of its own — it doesn't note that new posts default to draft status, what Remarkup rendering implies, or what a successful creation returns. With annotations carrying the safety profile, some context is missing but no contradiction exists.

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 short sentence with no filler, and the action is front-loaded. It is arguably too terse rather than wasteful, but every word earns its place.

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 tool with six parameters and no output schema, the schema supplies the field-level detail, so the core is complete. However, the description omits useful context such as the draft-default behavior and how to source a blogPHID, leaving the agent to infer from the schema.

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 the schema fully documents all six parameters including the visibility draft/published/archived meaning. The description adds nothing beyond the schema, so the baseline of 3 applies.

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 names a specific verb and resource ('Create a new Phame blog post'), which clearly distinguishes it from sibling operations like phabricator_blog_post_edit, phabricator_blog_post_search, and phabricator_blog_post_add_comment. It's clear but doesn't explicitly call out those alternatives.

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 guidance on when to use this versus phabricator_blog_post_edit or the search tool, and no mention of prerequisites such as obtaining a blogPHID. The draft-vs-published decision (visibility default 0) is left entirely to the schema.

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

Deploy Server