Mark an article as published
publish_articleRecords that an article went live on the user's site at the given address and marks it published, the same as saving the live URL in the PromptEye app.
Instructions
Records that an article went live on the user's site at the given address and marks it published, the same as saving the live URL in the PromptEye app. From then on PromptEye shows it as published content and follows whether the assistants cite that page. Call this once the user has published the text from get_article on their own site. The article must be written first — draft, ready, published or tracked are accepted; one still processing or in error is refused. Calling it again with another address replaces the URL and keeps the first publication date.
PromptEye generates content as well as measuring visibility, and the two make one loop: track the prompts and how often the assistants name the brand on them, generate an article that targets a prompt where the brand is weak, publish it, then measure whether that prompt's visibility and citations move. Generation starts from a content brief: PromptEye fans the target prompt out into the phrases people ask around it, keeps the ones that belong in this article, sets aside the ones that deserve an article of their own, and writes a title and an H2/H3 outline from them. create_content_brief orders one and get_content_brief reads it. create_article then writes the article from a ready brief, from the brand description, the knowledge documents picked for it and the chosen writing style; get_article reads its text and list_articles lists the project's articles, also those added in the app under Content (https://app.prompteye.com/content). Publishing the page is done on the user's own site; publish_article then records the URL it went live at, and requesting indexing and following citations happen in the app. A generated article is a draft to review, and neither it nor its indexing guarantees that an assistant will cite it. Guides: https://app.prompteye.com/help/content/ and https://app.prompteye.com/help/content/article-workflow/.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | The full http(s) address the article went live at. | |
| articleId | Yes | Id of the article, as create_article or list_articles reports it. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| error | Yes | Why the last generation failed. null unless status is error; content then still holds the previous version, if there was one. | |
| title | Yes | ||
| prompt | Yes | The target prompt the article was written for. | |
| source | Yes | generated_article when PromptEye wrote it from a brief, uploaded_docx or pasted when it was added in the app. | |
| status | Yes | processing while PromptEye writes it, then draft (the text is in content) or error. ready, published and tracked are later steps the team moves it through in the app. | |
| briefId | Yes | The content brief it was written from. null = text added to the app by hand. | |
| content | Yes | The article text in Markdown, with ## and ### headings. null until it is written. | |
| createdAt | Yes | When the article was created, ISO 8601 in UTC. | |
| projectId | Yes | ||
| updatedAt | Yes | When the article last changed, ISO 8601 in UTC. | |
| publishUrl | Yes | Where the article was published. null until it is. | |
| publishedAt | Yes | When it was published, ISO 8601 in UTC. null until it is. |