Skip to main content
Glama

Refresh an article

refreshArticle
Destructive

Rewrite only the sections of an article that have gone stale, using what people searched for when it was shown. The article as it was is kept, so the change can be compared and put back; the live post is unchanged until someone publishes it.

A change inside Kooga: it runs at once, as the person.

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": {
      "pieceId": "<pieceId>"
    },
    "name": "refreshArticle"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoWhy this article should be refreshed, citing what the read showed (an agent gives one)
pieceIdYesId from readDecaying - never invented
workspaceIdNoThe workspace, as listWorkspaces gives it (its id or slug). Leave it out when this connection reaches one workspace.
articleTitleNoWhat the article is called, as the read gave it, so the merchant sees which one

Output Schema

NameRequiredDescriptionDefault
statusYes
pieceIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / articleTitle
      Added value: +{
      +  "description": "What the article is called, as the read gave it, so the merchant sees which one",
      +  "maxLength": 255,
      +  "minLength": 1,
      +  "type": "string"
      +}
    • addedInput schema / properties / reason
      Added value: +{
      +  "description": "Why this article should be refreshed, citing what the read showed (an agent gives one)",
      +  "maxLength": 400,
      +  "minLength": 10,
      +  "type": "string"
      +}
  2. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources