Memos MCP Server

delete_shortcut

Remove a shortcut from a Memos instance by providing the instance and shortcut names. Deletes the specified shortcut permanently.

Instructions

Delete a shortcut.

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": {
      "instance": "<instance>",
      "shortcutName": "<shortcutName>"
    },
    "name": "delete_shortcut"
  }
}

Input Schema

Name	Required	Description	Default
`instance`	Yes	Instance name
`shortcutName`	Yes	Shortcut name

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Aug 30, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of disclosing behavior. 'Delete' indicates a destructive operation, but the description does not state whether deletion is permanent, whether the shortcut must exist, whether related data is affected, or what happens on success or failure. This is minimal behavioral disclosure.

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?

The description is a single, short sentence that is front-loaded and free of filler or redundancy. It is concise and readable, though terse to the point of under-specification; it still earns its place because no title is provided.

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?

Given the low tool complexity and full parameter coverage, the schema plus description provide enough for a basic invocation. However, with no annotations and no output schema, the description remains incomplete about side effects, prerequisites, and when to use this tool instead of related shortcut or delete tools.

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?

The input schema covers 100% of parameters with descriptions for 'instance' and 'shortcutName', so the baseline is 3. The description does not add any meaning beyond those schema descriptions, but no compensation is needed given full schema coverage and the simple parameter set.

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 uses a specific verb and resource, 'Delete a shortcut,' which clearly identifies the operation and distinguishes it from sibling delete tools by naming the shortcut resource. It lacks added scope or nuanced context beyond the tool name, but it is not vague or tautological.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives like update_shortcut, list_shortcuts, or delete_memo. There are no stated prerequisites, exclusions, or conditions or alternative routing. The only implied usage context comes from the tool name itself.

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

Deploy Server