Skip to main content
Glama
Sign In
phabricator-mcp

phabricator-mcp

by freelancer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

phabricator_blog_edit

Destructive

Create or edit a Phame blog in Phabricator; omit objectIdentifier to create a new blog with a required name, or provide an ID/PHID to update existing settings.

Instructions

Create or edit a Phame blog. Omit objectIdentifier to create a new blog (name is required for creation).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "phabricator_blog_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoBlog name
statusNoBlog status
subtitleNoBlog subtitle
parentSiteNoParent site name
descriptionNoBlog description (Remarkup)
parentDomainNoParent domain URL
domainFullURINoCustom full domain URI for the blog
objectIdentifierNoBlog PHID or ID. Omit to create a new blog.
addSubscriberPHIDsNoSubscriber PHIDs to add
removeSubscriberPHIDsNoSubscriber PHIDs to remove

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.19

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation risk is known structurally. The description adds the create-vs-edit precondition, but is silent on consequences of an edit (removed subscribers via removeSubscriberPHIDs, domain/parent changes) and on required permissions for a destructive operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, no filler, and the create/edit decision point is front-loaded in the second sentence where an agent will act on it.

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 10-parameter destructive write tool with no output schema, the description covers only the create/edit selector. It omits the destructive-edit consequences and the meaning of subscriber add/remove lists, which an agent needs before invoking it on an existing blog.

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 already explains every one of the 10 parameters. The description does add real value by asserting name is required for creation, which the schema does not mark as required. Beyond that it adds nothing on the subscriber, parentSite, or domain parameters.

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 pair and resource: 'Create or edit a Phame blog.' That distinguishes it from siblings like phabricator_blog_search and phabricator_blog_post_edit, though it does not explicitly name those siblings as alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit branch condition: omit objectIdentifier to create, include it to edit, and notes name is required for creation. It offers no guidance on when to use this versus blog_search (to locate a blog ID) or blog_post_edit, so it falls short of full routing guidance.

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