registry_upsert_taxonomy
Admin: up to 200 taxonomy nodes (sectors, industries, segments) by key, each under a parent key (default Universal). Creates or updates; unchanged nodes are left alone. Needs an admin key.
AdminMCP tool
Parameters
- nodesobject[]requiredmin 1 itemmax 200 items
- nodes[].keystringrequiredmin 1 charmax 80 charspattern ^[a-z0-9_]+$
- nodes[].namestringrequiredmin 1 charmax 120 chars
- nodes[].descriptionstringoptionalmax 2000 chars
- nodes[].parentstringoptional
Parent node key; omit for a top-level node under Universal
min 1 charmax 80 charspattern ^[a-z0-9_]+$ - nodes[].levelenumoptionaldefault "industry"sectorindustrysegment
- nodes[].sortOrdernumberoptional≥ 0≤ 10000
Example call
Agents call tools by name; you rarely write this by hand. It is here so you can test the server from a shell or your own code.
{
"name": "registry_upsert_taxonomy",
"arguments": {
"nodes": [
{
"key": "construction",
"name": "Construction",
"level": "industry"
},
{
"key": "specialty_contractors",
"name": "Specialty contractors",
"parent": "construction",
"level": "segment"
}
]
}
}Response
The result is one text content block holding this JSON (abbreviated here). Errors come back with isError: true and a message such as Error 401: … or Invalid input: ….
Response
{
"results": [
{
"key": "construction",
"id": "1d0f…",
"created": false,
"updated": false
},
{
"key": "specialty_contractors",
"id": "7a3c…",
"created": true,
"updated": false
}
]
}Over REST
The same call without MCP: POST/api/v1/admin/registry/taxonomy