Memos MCP Server

update_shortcut

Modify an existing shortcut's title or filter to keep saved Memos views accurate and current.

Instructions

Update an existing 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": "update_shortcut"
  }
}

Input Schema

Name	Required	Description
`title`	No	New title
`filter`	No	New filter expression
`instance`	Yes	Instance name
`shortcutName`	Yes	Shortcut name (e.g., "users/me/shortcuts/123")

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?

With no annotations present, the description carries the full burden of behavioral disclosure. It merely states that an existing shortcut is updated but does not explain whether fields are merged or overwritten, what permissions are required, or whether the operation is reversible.

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?

The description is a single short sentence with no filler or redundant content. It is appropriately sized for a simple CRUD operation and front-loads the core action.

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

Completeness2/5

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

Despite complete parameter documentation, the description lacks essential behavioral context for a mutation tool with no annotations or output schema. An agent doesn't know whether the update is partial or full, or what response to expect.

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 description coverage is 100%, so every parameter is already documented in the schema. The description adds no extra meaning beyond 'update', so a baseline score of 3 is appropriate.

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 clearly identifies the action ('update') and the resource ('existing shortcut'), which distinguishes it from sibling create/delete/list tools. It is concise and states the core purpose, though it does not specify which attributes are updatable.

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?

No guidance is provided about when to use this tool over create_shortcut, list_shortcuts, or other alternatives. The only implied context is that the shortcut must already exist, but no explicit selection criteria or exclusions are given.

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

Deploy Server