Skip to main content
Glama

Import list items

import_list_items
Destructive

Imports CSV or rows into a list: the first call previews; with confirm_token it saves as one change.

Input Schema

NameRequiredDescriptionDefault
csvNoWith a header row
listYes
rowsNoOr {field: value} each (id: change it)
siteYes
confirm_tokenNo
create_missingNoLink fields: add unknown names

Output Schema

NameRequiredDescriptionDefault
addNo
addedNo
previewNo
change_idNo
agent_messageNo
confirm_tokenNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedOutput schema / properties / add
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / added
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / agent_message
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / change_id
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / preview
      Added value: +{
      +  "type": "boolean"
      +}
  2. Changed2 schema fields changed
    • removedInput schema / properties / list / description
      Removed value: -"List name"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "confirm_token": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • removedInput schema / properties / confirm_token / description
      Removed value: -"From the first call"
  4. Changed2 schema fields changed
    • changedInput schema / properties / confirm_token / description
      Previous value: -"From the first call: approval status"New value: +"From the first call"
    • removedInput schema / properties / site / description
      Removed value: -"Site name"
  5. Changed6 schema fields changed
    • changedInput schema / properties / confirm_token / description
      Previous value: -"From the first call: re-call with it for the approval status"New value: +"From the first call: approval status"
    • removedInput schema / properties / csv / maxLength
      Removed value: -5000000
    • removedInput schema / properties / rows / items / additionalProperties
      Removed value: -{}
    • removedInput schema / properties / rows / maxItems
      Removed value: -20000
    • changedInput schema / properties / site / description
      Previous value: -"Site name, e.g. brave-otter-4821"New value: +"Site name"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": {},
      -  "properties": {
      -    "agent_message": {
      -      "type": "string"
      -    },
      -    "confirm_token": {
      -      "type": "string"
      -    },
      -    "error": {
      -      "description": "On failure (isError): {code, message}"
      -    }
      -  },
      -  "type": "object"
      -}New value: +null
  6. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare destructive=true, openWorld=true, and non-idempotency. The description adds important behavioral context beyond annotations: the first call is a preview, and confirm_token commits the import as one change, which partially mitigates the destructive profile.

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 a single front-loaded sentence with no wasted words. It conveys purpose and the most important two-phase behavior immediately.

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?

The output schema and annotations carry return values and safety signals, and the description covers the essential preview/confirm flow. Still, for a destructive six-parameter import tool, key parameters such as site, list, and create_missing remain unexplained, leaving meaningful gaps.

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?

With 50% schema description coverage, the description clarifies that csv and rows are alternative input formats and that confirm_token switches from preview to save. It does not explain site, list, or create_missing, so it only partially compensates for the schema gaps.

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: 'Imports CSV or rows into a list.' This clearly distinguishes bulk import from sibling tools like add_list_items or update_list_items, though it does not explicitly name alternatives.

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

Usage Guidelines3/5

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

It explains the two-step preview/confirm workflow, which is useful invocation guidance. However, it does not say when to use this tool instead of add_list_items, update_list_items, or save_list, so usage is implied rather than fully framed.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources