Cirra AI Salesforce Admin MCP Server

sobject_create

Create a new custom object (sObject) in Salesforce with specified sharing model, deployment status, and configuration options

Input Schema

Name	Required	Description
`label`	Yes	The human readable label for the field. If it is not provided, use the sObject property after stripping any suffix, replacing underscores with spaces and capitalizing the elements
`sObject`	Yes	The name of the object. For example, Account.
`sf_user`	No	(optional) Salesforce username to identify the connection to use. Omit this to use the current default connection.
`description`	No	Provides a description of the object's purpose. Generate a value for this if it is not provided
`pluralLabel`	Yes	The plural version of the human readable label for the field
`enableSearch`	No	Whether to enable search for the object. Default is false
`sharingModel`	Yes	Common options are `ReadWrite`, `Read` and `Private`
`cirra_ai_team`	No	(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit it when this call carries the context_handle from cirra_ai_init, which names the team for the conversation. A user with more than one place to work (several teams, or a team and a personal account) must pass either the context_handle or 'cirra_ai_team' + 'sf_user'.
`enableHistory`	No	Whether to enable field history tracking for the object
`enableReports`	No	Whether to enable reports for the object
`nameFieldType`	Yes	The type of the name field. Options are `AutoNumber` or `Text` (the default)
`context_handle`	No	(recommended) The conversation context handle returned by cirra_ai_init in this conversation. Pass the exact context_handle value from the most recent cirra_ai_init result so this call runs against the team and Salesforce connection selected for this conversation. A user with more than one place to work (several Cirra AI teams, or a team and a personal account) must pass either this handle or 'cirra_ai_team' + 'sf_user'; a call with neither is refused.
`nameFieldLabel`	No	The label for the name field. Defaults to `<obj label> Name`
`deploymentStatus`	Yes	Options are `Deployed` (the default) and `In Development`
`enableActivities`	No	Whether to enable activities for the object
`allowInChatterGroups`	No	Whether to allow the object to be used in Chatter groups
`nameFieldDisplayFormat`	No	For `AutoNumber` name fields only: the format to use for the display of the auto-number. For example, `A-{0000}`
`nameFieldStartingNumber`	No	For `AutoNumber` name fields only: the starting number for the auto-number. For example, `1000`

Output Schema

Name	Required	Description
`message`	Yes
`results`	No
`success`	Yes
`warning`	No
`errorCode`	No
`errorCount`	No
`resultCount`	No
`artifactType`	No
`requestCount`	No
`skippedCount`	No
`successCount`	No
`appliedMetadata`	No	The metadata payload that was actually sent to Salesforce for this operation (post-normalization/defaulting), so you can verify it matches what was intended without a separate read.
`artifactCategory`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 1, 2026

changedInput schema / properties / cirra_ai_team / description

Previous value: -"(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team."New value: +"(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit it when this call carries the context_handle from cirra_ai_init, which names the team for the conversation. A user with more than one place to work (several teams, or a team and a personal account) must pass either the context_handle or 'cirra_ai_team' + 'sf_user'."

addedInput schema / properties / context_handle

Added value: +{
+  "description": "(recommended) The conversation context handle returned by cirra_ai_init in this conversation. Pass the exact context_handle value from the most recent cirra_ai_init result so this call runs against the team and Salesforce connection selected for this conversation. A user with more than one place to work (several Cirra AI teams, or a team and a personal account) must pass either this handle or 'cirra_ai_team' + 'sf_user'; a call with neither is refused.",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "sObject",
-  "label",
-  "pluralLabel",
-  "description",
-  "nameFieldType",
-  "deploymentStatus",
-  "sharingModel"
-]New value: +[
+  "sObject",
+  "label",
+  "pluralLabel",
+  "nameFieldType",
+  "deploymentStatus",
+  "sharingModel"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "appliedMetadata": {
+      "additionalProperties": true,
+      "description": "The metadata payload that was actually sent to Salesforce for this operation (post-normalization/defaulting), so you can verify it matches what was intended without a separate read.",
+      "properties": {},
+      "type": "object"
+    },
+    "artifactCategory": {
+      "type": "string"
+    },
+    "artifactType": {
+      "type": "string"
+    },
+    "errorCode": {
+      "type": "string"
+    },
+    "errorCount": {
+      "type": "number"
+    },
+    "message": {
+      "type": "string"
+    },
+    "requestCount": {
+      "type": "number"
+    },
+    "resultCount": {
+      "type": "number"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {},
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "skippedCount": {
+      "type": "number"
+    },
+    "success": {
+      "type": "boolean"
+    },
+    "successCount": {
+      "type": "number"
+    },
+    "warning": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "success",
+    "message"
+  ],
+  "type": "object"
+}

Changed1 schema field changedJul 27, 2026

addedInput schema / properties / cirra_ai_team

Added value: +{
+  "description": "(optional) Cirra team ID or name that owns the Salesforce connection to use for this call. Must be provided together with 'sf_user'. Use it to run against a specific team's connection without changing your default team — e.g. to keep separate chats on Salesforce orgs in different teams. Omit to use your current/default team.",
+  "type": "string"
+}

AddedMay 8, 2026
RemovedMay 8, 2026
AddedFeb 26, 2026
RemovedFeb 26, 2026
Changed1 schema field changedFeb 20, 2026
- changedInput schema / additionalProperties
```
Previous value: -{}New value: +true
```
First observedJan 31, 2026

TDQS

C2.9/5.0

Behavior2/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=true, so the safety profile is covered. The description adds nothing beyond that: it doesn't say the change is an irreversible org metadata mutation, what permissions are required, or how name-conflicts on an existing sObject behave.

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?

A single front-loaded sentence with no filler. It is efficiently structured, though brevity here shades into under-specification given the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 18-parameter, 6-required org-mutating tool, the description omits the connection/context selection requirement, the fact that it creates metadata rather than data, and any caveats about naming or rollback. The output schema covers returns, but the call prerequisites an agent must satisfy are absent.

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%, so the schema already documents all 18 parameters including the tricky context_handle/cirra_ai_team interaction. The description only echoes three field groups (sharing model, deployment status, config options) without adding syntax or defaulting guidance, so it sits at the baseline.

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 ('Create a new custom object (sObject) in Salesforce') plus the main configuration axes. It is clear what the tool does, but it does not distinguish itself from nearby siblings like metadata_create or sobject_field_create, which plausibly also create org metadata.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus metadata_create or sobject_field_create, no prerequisites (permissions, connected org), and no mention that the required context_handle/cirra_ai_team connection selection must be supplied — a call with neither is refused.

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

All Cirra AI Salesforce Admin MCP Server tools Inspect

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

Need Help?