Skip to main content
Glama

Update Article Keys

update_article_keys
DestructiveIdempotent

Update an UNPUBLISH seliee_article (found by article_id or article_uuid); a PUBLISH article is refused with ERR_ARTICLE_NOT_UNPUBLISH. Allowed keys: seliee_article_publish_datetime (YYYY-MM-DD), seliee_article_slug (lowercase ascii words joined by hyphens), seliee_article_keywords (non-empty string). Any other key is refused and nothing is written.

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": {
      "updates": "<updates>"
    },
    "name": "update_article_keys"
  }
}

Input Schema

NameRequiredDescriptionDefault
updatesYes
article_idNo
article_uuidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations (readOnlyHint=false, destructiveHint=true): it discloses the specific error code ERR_ARTICLE_NOT_UNPUBLISH and states that a disallowed key causes nothing to be written, i.e. the update is atomic. That atomicity detail is exactly the kind of behavior annotations cannot express. It does not state permission/auth requirements, keeping it from 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.

Conciseness4/5

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

Three tight clauses: precondition, allowed keys with formats, failure/atomicity rule. Front-loaded with the constraint most likely to block the call. Slightly dense punctuation and the all-caps UNPUBLISH token cost a bit of readability but nothing is redundant.

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 mutation tool with no output schema and a nested free-form parameter object, the description supplies the essentials: eligibility, permitted keys, value syntax, and post-failure state. Missing only the return payload shape and the id-vs-uuid requirement, both minor against the coverage provided.

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

Parameters5/5

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

With 0% schema coverage on a nested, free-form `updates` object, the description carries the full burden and does so: it whitelists the three permitted keys and gives value formats for each (YYYY-MM-DD, lowercase ascii hyphen-joined slug, non-empty string), plus the rejection rule for everything else. The only gap is whether article_id or article_uuid is required, but the field-lookup semantics are otherwise well documented.

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

Purpose4/5

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

States a specific verb (update) plus the exact resource (seliee_article) and the fields it governs (keys). The added precondition – only UNPUBLISH articles – makes the tool's scope clearer than a bare name. It stops short of explicitly distinguishing itself from sibling edit_article, which an agent must infer.

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

Usage Guidelines3/5

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

Gives a clear use precondition (article must be unpublished) and the failure mode when it isn't, so the agent knows when the call will be rejected. However, it never names an alternative such as edit_article for published articles or for non-key fields, leaving the routing decision implicit.

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