Skip to main content
Glama
dnotitia

akb

by dnotitia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

akb_unpublish

Remove publication(s) by slug or resource URI. Use URI to clear every version tied to a resource before re-publishing; use slug for table-query publications without a URI. Returns deleted count.

Instructions

Remove publication(s). Pass slug to remove one specific publication, OR uri to remove every publication of that document/file resource (handy when re-publishing). table_query publications have no resource URI, so remove them by slug. Returns {deleted: N}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
uriNoDocument or file URI — remove every publication tied to that resource.
slugNoPublication slug — remove exactly this publication.
_vault_skill_ackNoOpaque acknowledgement returned as vault_skill.ack_token. After applying that guide, retry the unchanged operation with this value. The bundled proxy supplies it automatically.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.0.14
    • addedInput schema / properties / _vault_skill_ack
      Added value: +{
+  "description": "Opaque acknowledgement returned as vault_skill.ack_token. After applying that guide, retry the unchanged operation with this value. The bundled proxy supplies it automatically.",
+  "maxLength": 128,
+  "type": "string"
+}
  2. Changed2 schema fields changedv2.0.7
    • changedInput schema / properties / slug / description
      Previous value: -"Publication slug — deletes that specific publication"New value: +"Publication slug — remove exactly this publication."
    • changedInput schema / properties / uri / description
      Previous value: -"Resource URI — deletes all publications for this resource"New value: +"Document or file URI — remove every publication tied to that resource."
  3. Addedv2.0.4
  4. Removedv2.0.1
  5. First observedv0.1.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations provided, the description supplies the behavioral context: the operation is destructive, uri mode is broader than slug mode, table_query publications behave differently, and the return shape is {deleted: N}. It doesn't discuss irreversibility or permissions, but the removal semantics are clearly stated.

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 with no filler. The action, parameter choice, edge case, and return value are all packed efficiently, with the core instruction front-loaded.

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?

The description includes the return format, both invocation modes, and the exceptional table_query case, which is sufficient for normal use. It could be slightly more explicit that exactly one of slug or uri is expected, but 'Pass slug ... OR uri' conveys this reasonably.

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?

The schema already covers all parameters, so the baseline is 3. The description contributes extra meaning by explaining the OR relationship, the resource-wide effect of uri, and the table_query no-URI edge case.

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 opens with a precise verb and object, 'Remove publication(s)', and immediately distinguishes two scopes: slug for one specific publication, uri for all publications of a resource. This makes the tool's purpose obvious and separates it from sibling publication tools.

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 explicit conditions for choosing slug vs. uri, including the table_query exception ('remove them by slug'). It does not name alternative sibling tools, but the in-tool guidance is unambiguous and practical.

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

Deploy Server

Other Tools