Skip to main content
Glama
Sign In
appsmith-mcp

appsmith-mcp

by t0knight
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

delete_custom_themes

Delete multiple custom themes from your Appsmith application in a single API call, specifying theme IDs or names.

Instructions

Delete multiple saved custom themes in one tool call. Each entry is {"theme_id", "name"?}. name is looked up from the themes list per entry if omitted.

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": {
      "themes": "<themes>"
    },
    "name": "delete_custom_themes"
  }
}

Input Schema

NameRequiredDescriptionDefault
themesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations provided. Description discloses input format and that name can be looked up, but does not mention deletion behavior (idempotency, error handling, permissions) or return value. For a mutation tool with no annotations, more behavioral context 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with purpose. Efficient with no redundant information, though slightly more detail on behavior could be added without harming conciseness.

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?

Without output schema or annotations, description lacks behavioral details like success/failure, partial deletion, and permissions. For a deletion tool, these omissions reduce completeness.

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

Parameters4/5

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

Input schema has low coverage (0%), but the description explicitly details the structure of each entry: theme_id required, name optional with lookup behavior. This adds significant meaning beyond the bare 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?

Tool name and description clearly specify deleting multiple saved custom themes. The description uses a specific verb 'Delete' with resource 'custom themes' and distinguishes from sibling tools like save_custom_theme and update_theme.

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 states it deletes multiple themes in one call, implying batch deletion. It does not explicitly state when to use alternatives, but sibling tools cover other operations on custom themes, so context is clear.

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