Skip to main content
Glama
CRACKISH

mcp-creatio

by CRACKISH

Update record in Creatio

update

Update a Creatio record by ID with partial data using PATCH. Specify entity, record ID, and changed fields.

Instructions

Update a record by Id (PATCH). Supply entity, id, and partial data containing only changed fields. Examples: Account → data={ Name:'Updated Name' }; Contact → data={ Email:'new@example.com' }. DATE/TIME: For ANY date/time modifications (reschedule StartDate, set DueDate, reminders, custom date columns, CreatedOn override when allowed) consult /datetime-guide prompt (always send UTC). CONTACT/USER FIELDS: When changing OwnerId, AuthorId, ModifiedById (rare), ResponsibleId, ManagerId, etc use /contactid-guide prompt to resolve valid ContactId. Do NOT invent or reuse unrelated IDs. Activities: /create-activity-guide prompt (overall), /datetime-guide prompt (time changes), /contactid-guide prompt (participants/Owner).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesPrimary key of the record. Pass GUIDs as-is (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). Non-GUID strings will be quoted automatically.
dataYesPartial fields to change. Only include properties that should be updated. DATA TYPES: - Strings: "John Doe", "john@example.com" - Numbers: 1000, 25.99 - Booleans: true, false - Dates: ISO 8601 format with Z for UTC: "2025-10-08T19:00:00Z" - GUIDs (lookups): "8ecab4a1-0ca3-4515-9399-efe0a19390bd" (no quotes in value!) (same as create) ⏰ DATES & TIME: - Always use UTC time with Z suffix - Convert local time to UTC: subtract timezone offset - Format: "YYYY-MM-DDTHH:mm:ssZ" - Example: "2025-10-08T19:00:00Z" for 22:00 local (UTC+3) COMMON UPDATE SCENARIOS: - Change Activity time: { StartDate: "2025-10-09T14:00:00Z" } - Update status: { StatusId: "<GUID from ActivityStatus>" } - Reschedule with reminder: { StartDate: "...", RemindToOwnerDate: "..." } - Change account: { AccountId: "guid..." } 💡 For Activities: Query lookup tables (ActivityStatus, ActivityPriority) to get new IDs dynamically!
entityYesEntity set to update (e.g., Contact, Account).
Behavior3/5

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

No annotations are provided, so the description must carry the full burden. It states the tool is a PATCH update and gives details on partial data, but does not disclose side effects, rate limits, or what happens to omitted fields or errors.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but structured with sections for general use, examples, and special cases. It front-loads the main purpose but contains repetition and could be more streamlined.

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 description thoroughly covers input parameters but lacks information about the output (e.g., returned object, status code) and does not mention synchronicity or error behavior. Given no output schema, this is a gap.

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

Parameters5/5

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

Schema coverage is 100%, yet the description adds substantial value by explaining data types, date formatting, common scenarios, and cross-referencing specialized guides. This goes well beyond the schema's descriptions.

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 clearly states the tool updates a record by ID using PATCH, with specific verb, resource, and method. It provides examples for Account and Contact, and distinguishes itself from create/delete siblings.

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

Usage Guidelines4/5

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

The description gives clear usage context with examples and directs to specialized prompts for dates and contact IDs. However, it does not explicitly list conditions when not to use this tool versus alternatives like create or delete.

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/CRACKISH/mcp-creatio'

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