Skip to main content
Glama

Update article

update-article
Destructive

Update an article's title, slug, status (draft, ready or published), keywords, meta description, summary or Markdown body; only the fields sent change. A new body is refused while generating. Status published here does not push anywhere; publish-article does. A re-publish keeps the original publish date. updated lists the stored fields changed, including derived ones such as word count.

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": {
      "article_id": "<article_id>"
    },
    "name": "update-article"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugNoNew slug
titleNoNew title
statusNoNew status
summaryNoNew summary
keywordsNoNew keywords array
article_idYesArticle ID from list-articles
content_mdNoNew article body in Markdown; replaces the whole body
meta_descriptionNoNew meta description

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / article_id / description
      Previous value: -"Article ID"New value: +"Article ID from list-articles"
  2. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / article_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Changed1 schema field changed
    • addedInput schema / properties / content_md
      Added value: +{
      +  "description": "New article body in Markdown; replaces the whole body",
      +  "maxLength": 200000,
      +  "minLength": 1,
      +  "type": "string"
      +}
  4. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds substantive context beyond them: partial-update semantics ('only the fields sent change'), the body-edit refusal during generation, the re-publish date-retention behavior, and the fact that 'updated' lists stored fields including derived ones like word count. It does not state permission requirements or whether a destructive update is reversible, which keeps it short of a 5.

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?

A single dense paragraph with no filler; the field list is front-loaded, followed by the two behavioral caveats and the return-value note. Every clause carries information an agent would otherwise have to guess.

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

Completeness5/5

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

No output schema exists, so the description compensates by explaining what the 'updated' result contains. For a destructive 8-param mutation tool it covers the critical gaps: partial-update behavior, the generation lock on body edits, and the publish boundary against publish-article.

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 meaning the schema does not: 'only the fields sent change' explains why all seven non-required fields are optional and how partial updates behave, and the status values are restated alongside the publishing caveat. It goes modestly beyond the enum and per-field descriptions.

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?

Specific verb (update) plus resource (article) with an explicit enumeration of updatable fields (title, slug, status, keywords, meta description, summary, Markdown body). It also carves out a boundary against the sibling publish-article, so an agent can distinguish the two without opening either 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?

Explicitly states when not to rely on this tool for publishing ('Status published here does not push anywhere; publish-article does') and gives a conditional exclusion ('A new body is refused while generating'). Both the alternative and the blocking condition are named, leaving little inference.

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.

Resources