Skip to main content
Glama
KasayoDotCom

Identity Forge MCP

Official

Take a layer off a brand

remove_brand_layer

Remove a composed brand layer by permanent record ID while keeping the design kit and other axes. Confirmation is required to make the deletion permanent.

Instructions

Remove one composed record from a brand project. The brand keeps its design kit and every other axis; only this reference goes. Name the record rather than just the axis, so a stale view of the brand cannot clear a layer it never saw — pass the id you read from get_brand_layers rather than one you remember. Safe to repeat: an id that is not composed answers changed: false, changes nothing and mints no version. When the intent is to swap rather than to clear, call add_brand_layer with replace: true instead; removing first leaves the brand briefly without that axis and takes two versions to say one thing. This takes effect on the user's brand immediately and requires confirm: true; without it nothing changes. Requires the kits:write scope.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
axisYesWhich axis the record sits on.
confirmYesMust be exactly true. Required because removal is permanent.
recordIdYesPermanent id of the composed record, as reported by get_brand_layers.
projectIdYesOwned brand project id from list_brand_projects.
Behavior5/5

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

With no annotations, the description carries full burden and does so thoroughly: confirms permanence, requires confirm:true, states idempotency (changed:false, no version), immediate effect, and required kits:write scope. No contradictions.

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?

The description is front-loaded with the core action, and each subsequent sentence adds operational detail (idempotency, swap guidance, effect timing). Nothing is wasted.

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?

For a destructive mutation with no output schema, this covers prerequisites, side effects, alternatives, and error behavior comprehensively. The absence of output schema is mitigated by transparent no-op handling.

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

Parameters5/5

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

Despite 100% schema coverage, the description adds critical meaning: recordId should come from get_brand_layers not memory, confirm must be exactly true, and explains semantics of 'not composed' responses. This exceeds baseline.

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 opens with a specific verb-resource pairing: 'Remove one composed record from a brand project.' It clearly scopes the operation to a single layer reference and distinguishes from sibling add_brand_layer by stating what is NOT removed (design kit and other axes).

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?

Explicitly contrasts with add_brand_layer: 'When the intent is to swap rather than to clear, call add_brand_layer with replace: true instead.' Also instructs to pass the id read from get_brand_layers, preventing stale-data misuse.

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/KasayoDotCom/identityforge-mcp'

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