Skip to main content
Glama
lazyants

transkribus-mcp-server

by lazyants
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Bulk Update ISAD Metadata

transkribus_upload_bulk_update_isad_metadata
Idempotent

Bulk update ISAD(G) metadata for uploads using an inline CSV payload or a local CSV file path. Apply archival descriptions across multiple uploads in one request.

Instructions

Bulk update ISAD(G) metadata for uploads from a CSV payload.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
csvNoInline CSV content. Exactly one of "csv" or "csvFilePath" is required.
csvFilePathNoAbsolute path to a local CSV file. Exactly one of "csv" or "csvFilePath" is required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv4.0.0
    • addedInput schema / properties / csv
      Added value: +{
+  "description": "Inline CSV content. Exactly one of \"csv\" or \"csvFilePath\" is required.",
+  "type": "string"
+}
    • addedInput schema / properties / csvFilePath
      Added value: +{
+  "description": "Absolute path to a local CSV file. Exactly one of \"csv\" or \"csvFilePath\" is required.",
+  "type": "string"
+}
    • removedInput schema / properties / metadata
      Removed value: -{
-  "description": "Array of ISAD metadata objects to update",
-  "items": {
-    "additionalProperties": {},
-    "propertyNames": {
-      "type": "string"
-    },
-    "type": "object"
-  },
-  "type": "array"
-}
    • removedInput schema / required
      Removed value: -[
-  "metadata"
-]
  2. First observedv2.1.1

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and idempotentHint=true, so the mutation/idempotency profile is covered. The description adds only that input comes from a CSV, and says nothing about permissions required, which records are affected, or how partial failures behave. With annotations carrying the safety profile, a 3 is appropriate.

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?

A single front-loaded sentence with no padding. It is efficient, though it could carry one more clause of actionable detail without becoming bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a bulk mutation with no output schema, the definition covers the verb, resource, and input medium, but omits the CSV schema/column expectations and any response behavior. Adequate but with clear gaps an agent invoking a bulk metadata write would want filled.

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%, so both csv and csvFilePath are fully documented including the exactly-one-of constraint. The description's 'from a CSV payload' aligns with the schema but adds no format, delimiter, or column-mapping detail beyond it. 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?

States a specific verb and resource: bulk update ISAD(G) metadata for uploads, sourced from CSV. The ISAD(G) qualifier and 'bulk' distinguish it from the related upload_bulk_update_doc_metadata and upload_get_bulk_isad_metadata siblings, though it never names them 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?

No when-to-use guidance, no prerequisites, and no alternatives named. The sibling set contains get_bulk_isad_metadata (read side) and bulk_update_doc_metadata (non-ISAD variant), which an agent must disambiguate by name inference alone.

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