Skip to main content
Glama
Dynamics 365 MCP Server

Dynamics 365 MCP Server

by Kenny-666

execute_record_batch

Destructive

Run up to 100 validated Dynamics 365 record mutations in batched chunks, with preflight checks and per-item results for controlled bulk updates.

Instructions

Execute up to 100 validated record mutations in native $batch chunks. Each operation has its own change set, so a later failure does not roll back earlier operations. Preflights all operations before dispatch, reports per-item outcomes, stops after unknown results and respects request cancellation.

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": {
      "operations": "<operations>"
    },
    "name": "execute_record_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
dryRunNoCompatibility alias for dry_run. Conflicting aliases are rejected.
dry_runNoRead-only preview of environment, target, changes and write blockers. Default false; sensitive fields are masked.
chunkSizeNoCompatibility alias for chunk_size. Conflicting aliases are rejected.
chunk_sizeNoDefault 25. Every chunk must fit the 10 MiB wire-body limit.
operationsYes
continueOnErrorNoCompatibility alias for continue_on_error. Conflicting aliases are rejected.
continue_on_errorNoDefault false. Continue after known per-item rejection; unknown results always stop future chunks. Native support is not assumed when responses are incomplete.
environment_profileNoOptional named environment profile for this call; omit to use the configured default.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.1.2
    • addedInput schema / properties / environment_profile
      Added value: +{
      +  "description": "Optional named environment profile for this call; omit to use the configured default.",
      +  "pattern": "^[A-Za-z][A-Za-z0-9_]{0,31}$",
      +  "type": "string"
      +}
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Goes meaningfully beyond the destructiveHint=true / idempotentHint=false annotations by disclosing preflight validation, per-operation change sets, absence of rollback for earlier items, per-item outcome reporting, and stop-on-unknown-result behavior. These are exactly the partial-failure semantics an agent needs before committing a destructive batch; only permissions/rate-limit context is missing.

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?

One front-loaded sentence with the verb, cap, and mechanism first, followed by failure-semantics clauses that each carry information. It is dense and slightly run-on ('stops after unknown results and respects request cancellation') but no clause 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, 8-parameter tool with six operation variants and no output schema, the description covers the critical decision inputs: batch limit, chunking, non-atomicity, preflight, and per-item results. It omits any mention of the supported operation types and the dry_run preview path, both of which the schema documents, so the gap is small.

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 88%, so the schema already explains dry_run, chunk_size, continue_on_error, if_match, and alternate_key semantics. The description only contributes the 'up to 100' ceiling, which duplicates maxItems, and adds nothing about chunk_size, continue_on_error, or dry_run behavior.

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 ('Execute ... record mutations') plus a hard scope ('up to 100', 'native $batch chunks'), which lets an agent recognize bulk mutation. It does not, however, name the sibling it most needs to be distinguished from, execute_record_transaction, whose atomic semantics are the opposite of the non-rollback behavior described here.

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?

Bulk usage is implied by the 100-operation cap and chunking, but there is no explicit statement of when to prefer this over create_new_record/update_existing_record/delete_record_by_id calls or over execute_record_transaction. No when-not conditions or prerequisites are given.

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