Skip to main content
Glama
larasrinath

Anaplan MCP

by larasrinath
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Remote

delete_list_items

Remove items from an Anaplan list by specifying item ID or code. Use get_list_items to retrieve identifiers before deletion.

Instructions

Remove items from a list (WARNING: irreversible). Specify id or code for each item. Use get_list_items to find values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdYesAnaplan workspace ID or name
modelIdYesAnaplan model ID or name
listIdYesList ID or name
itemsYesItems to delete (specify id or code for each)

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed7 schema fields changedv1.2.0
    • changedInput schema / properties / items / description
      Previous value: -"Items to delete"New value: +"Items to delete (specify id or code for each)"
    • addedInput schema / properties / items / items / properties / code
      Added value: +{
+  "description": "Item code to delete (alternative to id)",
+  "type": "string"
+}
    • changedInput schema / properties / items / items / properties / id / description
      Previous value: -"Item ID to delete"New value: +"Item ID to delete (from get_list_items)"
    • removedInput schema / properties / items / items / required
      Removed value: -[
-  "id"
-]
    • changedInput schema / properties / listId / description
      Previous value: -"List ID"New value: +"List ID or name"
    • changedInput schema / properties / modelId / description
      Previous value: -"Anaplan model ID"New value: +"Anaplan model ID or name"
    • changedInput schema / properties / workspaceId / description
      Previous value: -"Anaplan workspace ID"New value: +"Anaplan workspace ID or name"
  2. Addedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Warns that the operation is irreversible, which is key behavioral info. However, it does not disclose other aspects like permissions or error handling, and annotations are absent.

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, no wasted words. The warning is front-loaded.

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?

Covers purpose, usage, and a key behavioral trait. Could mention error or success response, but overall adequate for a delete tool with no output schema.

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%; the description adds the 'irreversible' warning and usage hint but no new parameter-specific semantics beyond what the schema provides.

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 it removes items from a list, using the verb 'Remove'. It distinguishes itself from siblings like add_list_items or get_list_items.

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?

Provides explicit guidance to use get_list_items to find values before deletion. No explicit when-not-to-use, but the context is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/larasrinath/anaplan-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server