Skip to main content
Glama

Remove Labels from a Niche

remove_niche_labels
Destructive

Removes a niche from one or more labels by label ID, returning which labels were removed or already absent. Changes are all-or-nothing.

Instructions

Use this to take a niche out of one or more labels (ids from list_labels). Returns removed and notPresent. Undo with add_niche_labels. The same rights as the web app: the user needs Manage access to the niche, and to every Space added or removed. A refusal is a 403, so tell the user instead of retrying. A change is all or nothing: if any id is unknown, or a Space is one the user has only view rights on, the whole call fails and nothing changes (the error lists the offending ids). Ids already in the wanted state are counted, never errors, so a repeat is safe. Costs nothing. Limited to 2 calls per minute per niche, so put every id in one call.

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": {
      "nicheId": "<nicheId>",
      "labelIds": "<labelIds>"
    },
    "name": "remove_niche_labels"
  }
}

Input Schema

NameRequiredDescriptionDefault
nicheIdYesThe niche to change. Get one from `list_niches`.
labelIdsYesThe ids of the labels to take the niche out of, 1-100, unique. Get them from `list_labels`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.20.1

TDQS

A4.6/5.0
Behavior5/5

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

Far exceeds the annotations (readOnly=false, destructive=true) by disclosing the required Manage rights on the niche and every affected Space, the all-or-nothing transaction semantics, that offending ids are listed in the error, idempotency ('a repeat is safe'), zero cost, and a 2-calls-per-minute-per-niche rate limit.

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?

Front-loaded with purpose, return fields, and the undo path, then proceeds through permissions, errors, atomicity, and limits. Dense but nearly every clause carries operational information; a couple of clauses (e.g. 'Costs nothing') could be trimmed without loss.

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?

No output schema exists, yet the description names the returned fields (`removed`, `notPresent`) and explains failure shape, so an agent knows both how to call it and what to expect back. Nothing material is missing for a two-parameter mutation.

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% and already documents both parameters, their ranges, uniqueness, and the `list_labels` source, so the description mostly reinforces rather than adds. The added value is indirect: the rate-limit note tells the agent to pack all ids into one call, but no format or id-syntax meaning beyond the schema is given.

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?

States a specific verb and resource ('take a niche out of one or more labels') and implies the inverse sibling by naming `add_niche_labels` as the undo path, so an agent can distinguish the two immediately.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit routing: use `list_labels` for ids, undo via `add_niche_labels`, and batch all ids into a single call. It also gives a clear when-not-to-retry rule: a 403 refusal must be reported to the user rather than retried.

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