Propose an article
Draft/propose a long-form article for DEV (devdotto), Hashnode, Qiita, TabNews, Ghost or WordPress, with its title, markdown body, canonical link, tags,...
POST /api/v1/propose_article · MCP tool propose_article · scope drafts
Draft/propose a long-form article for DEV (devdotto), Hashnode, Qiita, TabNews, Ghost or WordPress, with its title, markdown body, canonical link, tags, cover image, native-draft flag, a requested publish time and per-network options. Does NOT publish and does NOT schedule: it saves a pending draft in the brand's Inbox, by code, with no model credits, and returns its proposalId. Only a human can approve it, on the Inbox card. The canonical link goes in the network's own field (DEV canonical_url, Hashnode originalArticleURL, Ghost canonical_url, TabNews source_url); Qiita and core WordPress have no such field, so the body gets an "Originally published at" line. A DEV article must state platformOptions.aiDisclosureLevel.
Scope. Save drafts, articles and series proposals to the Inbox, and withdraw your own drafts. Nothing publishes. This endpoint never costs credits.
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
platform | "devdotto" | "hashnode" | "qiita" | "tabnews" | "ghost" | "wordpress" | Yes | The article network. |
title | string | Yes | One line. The network's own title limit applies. |
body | string | Yes | Markdown body, without the title. |
canonicalUrl | string | No | https URL of the original (e.g. the article on your own site). |
tags | string[] | No | Tags without #. The network's limit applies: DEV 4, Qiita 5 (at least 1), Hashnode 15. |
coverImageUrl | string | No | https URL of an already-hosted cover image. DEV, Hashnode and Ghost only. |
draft | boolean | No | true: when a person approves, the network gets a native DRAFT (or private item) instead of a live post. |
scheduledAt | string | No | Requested publish time, ISO 8601 with a zone. Shown in the Inbox and the Calendar; a person confirms it. |
platformOptions | object | No | Network-native fields. devdotto: aiDisclosureLevel (required: no_ai | some_ai | fully_autonomous), series, description, organizationId. hashnode: subtitle. ghost: visibility, featured, slug, customExcerpt, meta/og/twitter fields. tabnews: slug. qiita: private, slide, tags [{name, versions}], organizationUrlName, postingCampaignUuid. wordpress: resource, slug, excerpt, commentStatus, pingStatus, format, sticky, categories. Any other key is refused by name. |
originallyPublishedLine | boolean | No | Qiita and WordPress only (no canonical field): false = do not add the "Originally published at" line to the body, e.g. when the body already credits the source. Default true. The line is in Japanese on a Japanese article. |
Request
curl -X POST https://growsocialelion.com/api/v1/propose_article \
-H "Authorization: Bearer gse_mcp_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"platform":"devto","title":"How we cut our build time in half","body":"## The problem\n\nOur CI took 14 minutes...","tags":["webdev","ci"]}'Response
200 with the tool's answer. The shape below is generated from the output schema; real answers can carry more fields.
{
"status": "string",
"reason": "string",
"proposalId": "string",
"published": false
}Errors use the shared body. See Errors. The full schema is in the API reference.