Skip to main content
Glama
Sign In
addy-mcp

addy-mcp

by Former-Stranger
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

delete_label

Destructive

Remove a label from an addy.io account while keeping its aliases; aliases stay but become unlabelled, so you can clean up labels without affecting email aliases.

Instructions

Delete a label (aliases are kept, just unlabelled).

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": {
      "label_id": "<label_id>"
    },
    "name": "delete_label"
  }
}

Input Schema

NameRequiredDescriptionDefault
label_idYesThe id (UUID) of the item

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds genuinely useful scope information - aliases are kept, only unlabelled - which refines what 'destructive' means here. It does not say whether the label row itself is permanently unrecoverable or what happens if the id is unknown.

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?

A single short sentence with the action front-loaded and the important side effect in parentheses. No padding or redundancy.

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?

For a one-parameter mutation with no output schema and full schema coverage, the description answers the main risk question an agent would have - whether deleting a label strips alias assignments. Minor gaps remain around permanence and error conditions, but the essentials are covered.

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?

Only one parameter, and the schema documents it at 100% coverage ('The id (UUID) of the item'). The description adds no meaning beyond that, so the baseline 3 applies.

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?

Specific verb (Delete) plus resource (a label), and the parenthetical clarifies the effect on aliases rather than restating the name. It implicitly separates the tool from delete_alias by stating aliases survive, though it never names a sibling explicitly.

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?

There is no when-to-use guidance, no prerequisites, and no pointer to alternatives such as bulk_set_alias_labels for removing a label across many aliases. The agent must infer that this is the tool for removing a single label definition.

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