Skip to main content
Glama
Sign In

Clueso

by io.clueso
OverviewDiscussionsAdmin

Update article

update_article

Update article text content from markdown. Use <SCREENSHOT {id}> placeholders to position screenshots. Screenshots in the markdown are kept. Screenshots removed from markdown are deleted. Order in markdown defines final order. Keep each <EMBED {id}> placeholder unchanged, or what it stands for is deleted. Get the current article first with get_article, modify the markdown, then call this with the article_version of the article you edited (from get_article, or from your last add_article_media / update_article_media / update_article on it). If the article changed since, the update is refused: read it again and redo the change.

Input Schema

NameRequiredDescriptionDefault
markdownYesUpdated article content as markdown with <SCREENSHOT {id}> placeholders
project_idYesProject ID
article_versionNoThe article_version of the article this markdown was written from. Recommended: without it, an edit someone else made since is overwritten.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / article_version
      Added value: +{
+  "description": "The article_version of the article this markdown was written from. Recommended: without it, an edit someone else made since is overwritten.",
+  "type": "string"
+}
  2. Changed4 schema fields changed
    • removedInput schema / properties / context
      Removed value: -{
-  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
-  "type": "string"
-}
    • removedInput schema / properties / conversation_id
      Removed value: -{
-  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
-  "type": "string"
-}
    • removedInput schema / properties / llm_model
      Removed value: -{
-  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "project_id",
-  "markdown",
-  "context",
-  "llm_model"
-]New value: +[
+  "project_id",
+  "markdown"
+]
  3. Changed4 schema fields changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as \"a user\", \"the customer\", or \"an account\". Example: \"Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution.\"",
+  "type": "string"
+}
    • addedInput schema / properties / conversation_id
      Added value: +{
+  "description": "Echo the conversation_id from the server's previous response. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it.",
+  "type": "string"
+}
    • addedInput schema / properties / llm_model
      Added value: +{
+  "description": "The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. \"claude-opus-4-8\", \"gpt-5.2\"). Used for analytics only. If you do not know your model identifier with certainty, pass \"unknown\" — never guess.",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "project_id",
-  "markdown"
-]New value: +[
+  "project_id",
+  "markdown",
+  "context",
+  "llm_model"
+]
  4. Changed2 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / additionalProperties
      Removed value: -false
  5. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Discloses non-obvious side effects the annotations do not: screenshots dropped from the markdown are deleted, markdown order defines final order, and altered <EMBED> placeholders delete their referents, plus optimistic-concurrency refusal on stale versions. One tension worth noting: annotations say destructiveHint=false while the description describes implicit deletions; and it doesn't say whether non-markdown article content (elements, media) survives an update.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action, then the placeholder rules, then the workflow — all sentences carry information. It is dense and slightly repetitive with the article_version schema text, but nothing is wasted.

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?

With no output schema and a mutating tool, the description covers workflow, versioning, and deletion semantics well. The remaining gap is what an update does to article parts not represented in the markdown (elements, existing media outside screenshots/embeds).

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 parameter definitions are already documented, but the description adds real meaning: where article_version comes from and why omitting it loses concurrent edits, plus the SCREENSHOT/EMBED placeholder conventions that govern the markdown string. It stops short of explaining what the id format in placeholders looks like.

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 verb and resource ("Update article text content from markdown") and immediately scopes it: text content only, with screenshots positioned via placeholders. That distinguishes it clearly from update_article_media and update_elements among the siblings.

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?

Gives an explicit sequence — get_article first, modify markdown, then call this with the article_version from get_article or the last add_article_media/update_article_media/update_article — and states what to do on refusal (read again and redo). No inference required.

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

All Clueso toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources