Skip to main content
Glama
chrischall

zola-mcp

by chrischall
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

remove_poi

Destructive

Delete a point-of-interest from the public Things-to-Do page after user confirmation. Prevents accidental removals.

Instructions

Remove a point-of-interest from the public Things-to-Do page. Asks the user to confirm first: a confirmation prompt where the client supports one; otherwise the first call returns a preview and a confirmToken, and only a repeat call with that token proceeds (see MCP_CONFIRM_MODE).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmTokenNoONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 "confirmation-required" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.
poi_entity_idYesPOI ID from list_pois

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.1.4
    • addedInput schema / properties / confirmToken
      Added value: +{
+  "description": "ONLY for the two-step confirmation fallback (a client without MCP elicitation). The confirmToken from this same tool's phase-1 \"confirmation-required\" response, passed back ONLY after the user has seen that preview and explicitly approved it in chat — never on the first call, never invented, never reused. Call again with the same arguments. Ignored when the client supports elicitation.",
+  "type": "string"
+}
    • addedInput schema / properties / poi_entity_id / description
      Added value: +"POI ID from list_pois"
  2. Changed1 schema field changedv2.0.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv1.4.2

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses the confirmation prompt behavior, the two-step fallback with preview and confirmToken, and the requirement to repeat the call with the token. These are critical non-obvious behaviors that ensure safe and correct invocation.

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 redundancy: the first states the core action, the second explains the confirmation protocol. Every sentence contributes essential information and is well front-loaded.

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

Completeness5/5

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

Given the tool's complexity—destructive action with a two-step confirmation flow—the description covers the non-obvious behavior (preview, confirmToken, repeat call) sufficiently for an agent to invoke it correctly. The schema handles parameter details and the annotation confirms destructiveness.

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 the baseline is 3. The description references confirmToken in context but does not add meaning beyond what the schema already provides; all important parameter details (POI ID source, token rules) are already in the schema.

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 uses a specific verb ('Remove') and a specific resource ('point-of-interest from the public Things-to-Do page'), making the tool's action unambiguous. It clearly distinguishes itself from sibling POI tools like add_poi, update_poi, and list_pois.

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?

The description gives clear context for when the tool is used (to remove a POI from the public Things-to-Do page) and provides detailed operational guidance for the confirmation flow. It does not explicitly name alternatives or when-not-to-use conditions, but the purpose is self-evident relative to siblings.

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