Skip to main content
Glama
Sign In

Widely

by com.widely-mobile
OverviewDiscussionsAdmin

Create CRM records

crm_bulk_create

Creates many records on one list by saving one row at a time. At most 50 rows. dry_run checks every row and saves nothing. The result lists each row that was saved and each row that was refused.

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": {
      "model": "<model>",
      "records": "<records>"
    },
    "name": "crm_bulk_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYesList name on this account.
dry_runNoWhen true, check every row and save nothing.
recordsYesRows to create. At most 50.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare it is a non-read-only, non-destructive, non-idempotent, open-world write, so the description only needs to add context. It does: it discloses that rows are committed individually (partial success is possible), that the run is capped at 50, and that dry_run validates without persisting, plus that the result enumerates both saved and refused rows. What is missing is why a row gets refused and whether a failed row aborts the rest.

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 a distinct fact: verb/resource, per-row commit model, row cap, dry_run behavior, and return shape. Nothing is repeated and the key constraint is front-loaded.

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?

With no output schema, the description correctly takes on the job of explaining the return value (per-row saved vs refused), which is the main thing an agent needs to interpret results. For a mutating, non-idempotent bulk tool it could still say more about failure handling and retry safety, so it stops short of complete.

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 100% and every parameter (model, records, dry_run) is documented in the schema, so the baseline is 3. The description restates maxItems=50 and dry_run semantics without adding meaning beyond the schema, so it does not earn a 4.

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 gives a specific verb and resource ("Creates many records on one list") and adds the mechanism ("saving one row at a time"), which distinguishes it from a single-record tool. It never names the obvious sibling (crm_create), so the differentiation is implicit rather than explicit.

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 50-row cap and the dry_run note give implied usage context for batch creation, but there is no explicit statement of when to use this over crm_create or crm_update, and no prerequisite guidance (permissions, required fields, shape of a list). The guidance is inferable rather than stated.

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

All Widely toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources