TypeWriter MCP

delete_entry

Delete an entry from a Typewriter page by providing its unique entry ID. Helps manage storyline entries by removing unwanted or outdated data.

Instructions

Delete an entry by id.

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": {
      "page": "<page>",
      "entryId": "<entryId>"
    },
    "name": "delete_entry"
  }
}

Input Schema

Name	Required	Description	Default
`page`	Yes
`entryId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.0.0Aug 14, 2026

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations available, the description must disclose behavioral traits on its own. It only states 'delete,' which implies destructiveness, but doesn't clarify permanence, cascading effects, or prerequisites. The agent is left without information about what happens to related data or whether confirmation is needed.

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, front-loaded sentence with no redundant words. It states the action and the key identifier efficiently, earning its place despite being minimal.

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?

Given the tool has two required parameters, no output schema, and no annotations, the description is insufficient. It fails to explain the 'page' parameter, the behavior on deletion, or any side effects. The tool is simple but still incomplete for safe and correct usage.

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

Parameters1/5

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

Schema description coverage is 0%, so the description must explain the parameters. It only hints at entryId via 'by id,' but completely ignores the required 'page' parameter. An agent would not understand the role of 'page' or how it interacts with entryId, making it impossible to invoke the tool correctly.

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 clearly states the verb (delete), the resource (entry), and the identification method (by id). It effectively distinguishes from sibling tools like delete_page and update_entry, making its purpose specific and unambiguous.

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. It doesn't mention that it's for removing an entry from a page, nor does it clarify relationships with sibling tools like delete_page or add_entry. There are no usage contexts or exclusions.

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

Deploy Server