Skip to main content
Glama

Write and manage articles

manage_articles
Destructive

Write, edit, rewrite, delete or restore an article. Never publishes. operation: draft = write a draft for a question, or for a planned article_id; edit = change the title, meta or exact words of a written article (title, meta, replacements); refresh = rewrite a written article with the current brand profile; delete = move to Trash (restorable); restore = bring back from Trash. Without confirm: true NOTHING changes: you get a preview. Show it to the user and call again with confirm: true only after they approve it.

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": {
      "operation": "<operation>"
    },
    "name": "manage_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault
metaNoOnly for operation edit. New meta description.
brandNoBrand id, name or domain (from get_account (view: brands)). Optional when the account has a single brand.
titleNoOnly for operation edit. New title.
confirmNoLeave out (or false) to get a preview: nothing changes. Set true ONLY after the user approved that exact preview.
languageNoOnly for operation draft. Only when the article must be written in another language than the brand's, e.g. "English (en)" for the action english:fanout. Omit otherwise.
questionNoOnly for operation draft, refresh. The buyer question the article must answer, e.g. a prompt from get_prompts (view: gaps).
operationYesWhat to do.
article_idNoOr the id of a PLANNED article of the content plan (get_content (view: plan)): writes that topic in place.
replacementsNoOnly for operation edit. Find-and-replace edits in the body, applied in order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description goes further by explaining that delete is soft (moves to Trash and is restorable) and that nothing mutates without confirm: true. That preview-then-commit contract is behavioral context the annotations cannot express, and it materially changes how an agent should sequence the call.

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?

Front-loaded with the verb list and the non-publishing constraint, then a compact semicolon-delimited operation glossary, then the safety rule. Every clause carries information; there is no restating of the tool name or filler prose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter mutation tool with full schema coverage and no output schema, the description covers operation semantics, the confirm contract, and parameter-to-operation mapping. The only gap is what a preview or a successful delete/restore returns, which an agent may want to know before echoing results to the user.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real mapping value by tying parameters to operations (title/meta/replacements belong to edit, question to draft and refresh) and by noting article_id may reference a planned article so the topic is written in place. It does not explain ordering or format of replacements beyond "applied in order", which the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific set of verbs (write, edit, rewrite, delete, restore) against a concrete resource (article), and immediately bounds it with "Never publishes", which separates it from the sibling publish_article. An agent can classify the tool without opening the schema.

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

Usage Guidelines5/5

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

Each enum value is given a when-to-use condition: draft for a question or planned article_id, edit for title/meta/exact wording, refresh for rewriting against the current brand profile, delete for Trash, restore for recovery. The confirm gate is also given an explicit ordering rule (preview, show user, then confirm).

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.