Skip to main content
Glama

Import multiple collection entries

import_collection
Destructive

Saves collection counts in one operation. Match every row to a datasheet id with list_units. Use replace false to keep existing counts. Use true only after explicit confirmation to overwrite counts on matching entries. Entries omitted from the import stay in the collection, so imports can be split into batches. Requires mcp:manage.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "rows": "<rows>",
      "replace": "<replace>"
    },
    "name": "import_collection"
  }
}

Input Schema

NameRequiredDescriptionDefault
rowsYes
replaceYes
llm_modelNoThe model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
conversation_idNoThe conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already flag destructive=true and openWorld=true; the description adds real value on top by naming what is destroyed (existing counts on matching entries), what is preserved (entries omitted from the import), and the required scope (mcp:manage). It does not address atomicity or partial-failure behavior across up to 5000 rows, which matters for a destructive bulk write.

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?

Four short sentences, each carrying distinct information: purpose, prerequisite, the replace flag's two modes, batching/preservation semantics, and permission scope. Purpose is front-loaded and nothing is filler.

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

Completeness4/5

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

For a destructive bulk mutation with no output schema, the definition covers the risky parts an agent needs: overwrite vs. merge behavior, confirmation requirement, scope enforcement, and batching safety. Missing only failure/atomicity expectations, which would matter at 5000-row scale.

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

Parameters4/5

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

Schema description coverage is 50% – the two analytics params are documented in-schema but rows and replace are not. The description compensates well for replace by spelling out the overwrite semantics, and clarifies that rows must carry datasheet ids resolved via list_units. It adds nothing about countsAs, the numeric bounds, or the 5000-row cap.

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?

Uses a specific verb and resource ('Saves collection counts in one operation') and names the prerequisite sibling list_units for resolving entry ids. An agent can tell it apart from the single-field setters such as set_collection_counts_as, though it never explicitly contrasts itself with them.

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?

Gives explicit conditional guidance: replace=false to keep existing counts, replace=true only after explicit user confirmation, omitted entries remain so imports can be batched, and rows must be matched to datasheet ids via list_units. That is when-to-use, when-not-to-use, and prerequisites in one place.

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