Skip to main content
Glama
Sign In
Drupal MCP Server

Drupal MCP Server

by vloganathane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Migrate Taxonomy

migrate_taxonomy

Migrate taxonomy vocabularies and their terms to this site.

Instructions

Migrate taxonomy vocabularies and their terms to this site.

Each vocabulary carries vid/id, name, description and optional terms. A term's tid/id is used only to find an existing term: JSON:API treats it as read-only and rejects it as a settable attribute.

Input Schema

NameRequiredDescriptionDefault
vocabulariesYes
include_termsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.8
    • removedInput schema / properties / source_jsonapi
      Removed value: -{
-  "anyOf": [
-    {
-      "type": "string"
-    },
-    {
-      "type": "null"
-    }
-  ],
-  "default": null
-}
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that a term's tid/id is read-only in JSON:API and is used only to find an existing term, but it does not state whether vocabularies/terms are created, updated, skipped, or overwritten, nor does it cover permissions, idempotency, or destructive effects.

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?

The description is short and front-loaded with the migration action. The second paragraph contains useful context rather than filler, though the dense ID/JSON:API explanation could be structured more cleanly.

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?

An output schema exists, so return values do not need to be explained here. However, for a migration tool with no annotations and a schema at 0% description coverage, the definition omits important context: source/prerequisites, conflict handling, whether existing content is updated or skipped, and what include_terms controls.

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 description coverage is 0%, so the description must carry parameter meaning. It adds useful detail for each vocabulary object, including vid/id, name, description, and optional terms, plus term-ID lookup behavior, but it does not mention the include_terms parameter at all.

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?

The description states a specific verb and resource: migrate taxonomy vocabularies and their terms to this site. It is distinguishable from plain vocabulary/term CRUD in general, but it does not explicitly name sibling alternatives such as create_vocabulary, create_term, export_taxonomy, or migrate_records.

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 explicit guidance on when to use this tool versus create_vocabulary/create_term, export_taxonomy, or migrate_records, nor are prerequisites or when-not-to-use conditions given. Usage is only implied by the tool name and the phrase 'to this site'.

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