Skip to main content
Glama

Delete article

delete_article
DestructiveIdempotent

Delete a help center article. Archiving it (update_article, status archived) keeps the text.

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": {
      "portal_slug": "<portal_slug>",
      "article_id": "<article_id>"
    },
    "name": "delete_article"
  }
}

Input Schema

NameRequiredDescriptionDefault
article_idYes
portal_slugYesPortal slug, as returned by list_portals.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is carried elsewhere. The description adds the useful nuance that archiving preserves text, which implicitly signals that deletion does not, but it never states permanence, permission requirements, or what happens to published/linked articles.

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 short sentences, zero waste, and the destructive action is stated first with the safer alternative immediately trailing. Nothing could be cut without losing the routing guidance.

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

Completeness3/5

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

For a simple two-parameter destructive tool with full annotations and no output schema, purpose and the archival alternative are covered. It still leaves the permanence of deletion implicit and says nothing about article_id, which is undocumented in the schema as well.

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

Parameters2/5

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

Schema description coverage is only 50% – portal_slug is documented in the schema but article_id is not. The description mentions no parameters at all, so it fails to compensate for the gap and adds nothing about identifier source or format.

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 and resource ('Delete a help center article'), which is enough for an agent to tell it apart from update_article or get_article. The only shortfall is that it doesn't clarify scope beyond 'help center article', so the exact object class relies on the sibling list rather than the text.

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 names the alternative and the condition that selects it: use update_article with status archived if the text should be kept. That is a direct when-to-use-this vs when-to-use-something-else rule with no inference required.

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