Skip to main content
Glama
CRACKISH

mcp-creatio

by CRACKISH

Create record in Creatio

create

Creates a new record in Creatio CRM. Provide entity name and field data map. Use 'describe-entity' to confirm required fields and types.

Instructions

Create a single Creatio record. Use 'describe-entity' first to confirm required fields & types. Provide entity and data map. Only include fields you need. ALL DATE/TIME FIELDS: For ANY date/time field (StartDate, DueDate, RemindToOwnerDate, CreatedOn overrides, custom date columns) ALWAYS use /datetime-guide for UTC conversion & formatting. ALL CONTACT / USER LOOKUP FIELDS: For ANY field pointing to a user/contact (OwnerId, AuthorId, CreatedById, ModifiedById, ResponsibleId, ManagerId, SupervisorId, and similar *Id fields referencing sys users) use /contactid-guide to resolve correct ContactId. Avoid guessing IDs. 🎯 DEFAULT OWNER/AUTHOR: Activities and tasks are ALWAYS created for the CURRENT USER by default! Set OwnerId and AuthorId to current user's ContactId (from get-current-user-info or SysAdminUnit.ContactId) unless user EXPLICITLY says "for [another person]". Don't ask "for whom?" - default to current user! Activities (Task/Meeting/Call/Email): HARD RULE → Always set TypeId to Task (fbe0acdc-cfc0-df11-b00f-001d60e938c6) and vary only ActivityCategoryId for meeting/call/email intent unless user explicitly says phrases like: "real meeting type", "true call type", "not a task", "use Visit type". Do NOT look up ActivityType for ordinary meeting/call/email requests. To intentionally allow a non-Task type, caller must add meta flag __allowNonTaskType=true. See /create-activity-guide prompt. Tagging: use /tagging-guide prompt. Examples: Account → data={ Name:'Acme Corp', Phone:'+1-234-567' }; Contact → data={ Name:'John Doe', Email:'john@example.com' }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesField map for new record. 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!) LOOKUP FIELDS: - Use field name ending with Id: AccountId, ContactId, TypeId, etc. - Value must be valid GUID from related entity - Example: AccountId: "8ecab4a1-0ca3-4515-9399-efe0a19390bd" ⏰ 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) 💡 TIP: Call 'describe-entity' first to see required fields and their types!
entityYesEntity set to create a record in (e.g., Contact, Account). Tip: use "describe-entity" to find required fields and types before creating.
Behavior5/5

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

Without annotations, the description carries full burden. It discloses important behaviors: activities default to current user, activity type hard rule, and that tagging requires a separate guide. No contradictions with annotations (none exist).

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?

The description is long but well-organized with bullet points and bold emphasis. Every sentence adds value, though some redundancy could be trimmed. Still, it's structured effectively for an AI agent.

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?

Given no output schema, it does not describe return values, but input is thoroughly covered. References to external guides enhance completeness. For a creation tool, this is adequate, though missing response details.

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%, and the description adds substantial value beyond schema fields: detailed data types, lookup field format, date/time conversion, and real examples. This compensates for any lack of schema detail.

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 explicitly states it creates a single Creatio record, and is clearly distinguishable from sibling tools like delete, update, read, and list-entities. It specifies the operation and resource.

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?

Provides explicit when-to-use guidance: 'Use describe-entity first to confirm required fields & types.' Also includes hard rules for activities (always set TypeId to Task unless meta flag) and default owner/author behavior. References external guides for complex cases.

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