Skip to main content
Glama

batch_update_items

Batch update multiple items in a Skema CMS collection by specifying the collection name and an array of items with their IDs and modified data.

Instructions

Met à jour plusieurs items en une seule requête

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionYesNom de la collection
itemsYesTableau d'items avec leur ID et les données à modifier

Implementation Reference

  • Tool definition for 'batch_update_items' with inputSchema requiring 'collection' (string) and 'items' (array of objects each with required 'id')
    {
      name: "batch_update_items",
      description: "Met à jour plusieurs items en une seule requête",
      inputSchema: {
        type: "object",
        properties: {
          collection: {
            type: "string",
            description: "Nom de la collection",
          },
          items: {
            type: "array",
            items: {
              type: "object",
              properties: {
                id: { type: "string" },
              },
              required: ["id"],
            },
            description: "Tableau d'items avec leur ID et les données à modifier",
          },
        },
        required: ["collection", "items"],
      },
    },
  • Handler case 'batch_update_items' extracting 'collection' and 'items' from args, then calling skema.batchUpdate(collection, items)
    case "batch_update_items": {
      const { collection, items } = args as {
        collection: string;
        items: Array<{ id: string } & Record<string, unknown>>;
      };
      result = await skema.batchUpdate(collection, items);
      break;
    }
  • Helper function 'batchUpdate' that calls the remote MCP API with 'batch_update_items' tool name, passing collection and items
    /**
     * Met a jour plusieurs items en une seule requete
     */
    export const batchUpdate = (
      collection: string,
      items: Array<{ id: string } & Record<string, unknown>>
    ) =>
      mcpCall("batch_update_items", { collection, items });
  • src/index.ts:30-32 (registration)
    Registration of all tools (including batch_update_items) via server.setRequestHandler(ListToolsRequestSchema) using the imported tools array
    server.setRequestHandler(ListToolsRequestSchema, async () => ({
      tools,
    }));
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only indicates a write operation but omits critical details: atomicity (all-or-nothing?), partial failure handling, idempotency, authentication requirements, rate limits, or any side effects. For a batch operation, this is insufficient.

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?

A single, concise sentence that front-loads the key purpose with no filler words. Every part is essential and efficiently communicated.

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?

Given the tool's batch update nature with no output schema or annotations, the description is adequate for basic understanding but leaves gaps: error handling, response format, and behavior on invalid items. For a straightforward tool, it is minimally viable.

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?

Input schema has 100% description coverage, so baseline is 3. The description adds marginal value by confirming the batch nature but does not elaborate on parameter formats or constraints (e.g., how to specify fields to update). Schema descriptions already handle the core meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description specifically states 'updates multiple items in a single request', clearly indicating the verb (update), resource (items), and scope (multiple, batch). This distinguishes it from siblings like update_collection_item (single item) and batch_create_items (create).

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?

The description implies usage for batch updates but gives no explicit guidance on when to use versus alternatives like single updates or batch creates. The context is minimally implied, lacking ‘when-not’ or explicit comparisons.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/skemacms/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server