Skip to main content
Glama

Docs MD: markdown workspace for AI agents

Delete a document

delete_share
DestructiveIdempotent

Permanently delete a document this agent owns. Documents created before 2026-11-13 have no owner agent: pass their edit_token instead of agent_key.

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": {
      "id": "<id>"
    },
    "name": "delete_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe document id (e.g. calm-river-Ab12C) or any docs-md.com URL of it.
agent_keyNoThe owner agent's key. Required unless edit_token is given.
edit_tokenNoOnly for documents created before 2026-11-13.

Output Schema

NameRequiredDescriptionDefault
idYes
deletedYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • addedInput schema / $schema
      Added value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / properties / agent_key
      Added value: +{
      +  "description": "The owner agent's key. Required unless edit_token is given.",
      +  "type": "string"
      +}
    • changedInput schema / properties / edit_token / description
      Previous value: -"Edit token returned when the share was created"New value: +"Only for documents created before 2026-11-13."
    • addedInput schema / properties / edit_token / maxLength
      Added value: +200
    • changedInput schema / properties / id / description
      Previous value: -"The share id (the URL path segment)"New value: +"The document id (e.g. calm-river-Ab12C) or any docs-md.com URL of it."
    • addedInput schema / properties / id / maxLength
      Added value: +300
    • addedInput schema / properties / id / minLength
      Added value: +1
    • changedInput schema / required
      Previous value: -[
      -  "id",
      -  "edit_token"
      -]New value: +[
      +  "id"
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "https://json-schema.org/draft/2020-12/schema",
      +  "additionalProperties": false,
      +  "properties": {
      +    "deleted": {
      +      "type": "boolean"
      +    },
      +    "id": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "deleted"
      +  ],
      +  "type": "object"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the bar is lower, but the description adds meaningful context beyond them: the operation is permanent and the authorization path differs depending on document creation date. It stops short of saying whether deletion is recoverable or what the response contains, but the key auth nuance is disclosed.

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 permanence warning and ownership scope front-loaded before the legacy-credential exception. Every sentence carries information the agent needs.

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 destructive, open-world tool with a full input schema and an output schema, the description covers what is destroyed and how to authenticate in both cases. Only the post-delete state (what a repeat call on an already-deleted id does) is left implicit, which is minor given idempotentHint.

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

Parameters3/5

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

Schema coverage is 100%, so id, agent_key and edit_token are already documented, including the 'required unless edit_token is given' rule. The description restates that either/or choice and the date boundary for edit_token rather than adding new semantics, so it sits at the baseline.

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?

The description states a specific verb and resource ('Permanently delete a document') and adds a scope qualifier ('this agent owns') that separates it from read_share and update_share. It does not name an alternative, but the ownership/irreversibility framing makes the purpose unambiguous.

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?

It implies the precondition (you must own the document) and tells the agent which credential applies to legacy documents, which is real conditional guidance. However, it never says when to use this versus update_share or what to do if ownership fails, so selection guidance is only implied.

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.