Skip to main content
Glama

Edit Article

edit_article
DestructiveIdempotent

Correct the publish date (seliee_article_publish_datetime, YYYY-MM-DD) of an UNPUBLISH seliee_article, found by article_id or article_uuid. This is the only field it changes; a PUBLISH article is refused with ERR_ARTICLE_NOT_UNPUBLISH.

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": {
      "seliee_article_publish_datetime": "<seliee_article_publish_datetime>"
    },
    "name": "edit_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
article_idNo
article_uuidNo
seliee_article_publish_datetimeYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedInput schema / properties / seliee_article_content
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Seliee Article Content"
      -}
    • removedInput schema / properties / seliee_article_description
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Seliee Article Description"
      -}
    • removedInput schema / properties / seliee_article_faqs
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "items": {
      -        "additionalProperties": true,
      -        "type": "object"
      -      },
      -      "type": "array"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Seliee Article Faqs"
      -}
    • removedInput schema / properties / seliee_article_keywords
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Seliee Article Keywords"
      -}
    • addedInput schema / properties / seliee_article_publish_datetime
      Added value: +{
      +  "title": "Seliee Article Publish Datetime",
      +  "type": "string"
      +}
    • removedInput schema / properties / seliee_article_slug
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Seliee Article Slug"
      -}
    • removedInput schema / properties / seliee_article_title
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Seliee Article Title"
      -}
    • removedInput schema / properties / seliee_article_type
      Removed value: -{
      -  "anyOf": [
      -    {
      -      "type": "string"
      -    },
      -    {
      -      "type": "null"
      -    }
      -  ],
      -  "default": null,
      -  "title": "Seliee Article Type"
      -}
    • addedInput schema / required
      Added value: +[
      +  "seliee_article_publish_datetime"
      +]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations it discloses two things the structured data does not: that exactly one field is mutated (narrowing what destructiveHint=true actually means in practice) and the specific error code returned for a published article. It does not mention required permissions or what happens with an invalid date, which keeps 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.

Conciseness5/5

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

Two sentences, zero filler, with the mutated field front-loaded and the refusal condition following immediately. Every clause adds information an agent needs before calling.

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 three-parameter mutation with no output schema, it covers the scope of the write, the precondition, the failure mode, and the value format. Remaining gaps are permission requirements and identifier precedence, which are secondary for correct invocation.

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 description coverage is 0%, so the description must carry parameter meaning and it largely does: it gives the value format (YYYY-MM-DD) for the required datetime and explains that article_id or article_uuid is the lookup key, clarifying an implicit either/or that the schema does not enforce. It leaves open whether both identifiers may be supplied or which wins.

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?

The description names a specific verb and resource (correct the publish date of an UNPUBLISH seliee_article), names the exact field affected, and scopes the operation to a single attribute. That distinguishes it from broader siblings such as edit_articles_order or create_article without requiring the agent to open their schemas.

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

Usage Guidelines4/5

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

It gives a clear precondition (the article must be unpublished) and an explicit failure case for published articles, which is the key routing decision for this tool. It stops short of naming the alternative to use when the article is published or when a different field needs changing, so the agent must infer those routes.

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.