Cirra AI Salesforce Admin MCP Server

sobject_field_create

Create a new custom field for an sObject in Salesforce

Input Schema

Name	Required	Description
`label`	Yes	The label for the field
`sObject`	Yes	The API name, label or ID of the sObject
`sf_user`	No	(optional) Salesforce username to identify the connection to use. Omit this to use the current default connection.
`fieldName`	Yes	The API name of the new field. For example, NewField__c
`fieldType`	Yes	The type of the field
`defaultFLS`	No	The default Field-Level Security (FLS) setting to apply for all profiles for the new field
`properties`	No	A map of properties used when creating the field. Some may be required, depending on the field type. See instructions for details
`description`	No	The description for the field. Recommended, but not required -- omit it, or pass '' or null, if the user asked for no description.
`flsOverrides`	No	An (optional) array of Field-Level Security (FLS) overrides for one or more profiles
`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'.
`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.
`inlineHelpText`	No	The inline help text for the field. Recommended, but not required -- omit it, or pass '' or null, if the user asked for no help text.

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 CustomField metadata that was actually sent to Salesforce, including any values the server filled in (e.g. defaulted or 'length'-alias-derived precision/scale). Use this to verify the field was created exactly as intended.
`artifactCategory`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedNov 1, 2026

addedInput schema / additionalProperties
```
Added value: +false
```

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 / properties / description / description

Previous value: -"The description for the field"New value: +"The description for the field. Recommended, but not required -- omit it, or pass '' or null, if the user asked for no description."

addedInput schema / properties / flsOverrides / items / additionalProperties
```
Added value: +false
```

changedInput schema / properties / inlineHelpText / description

Previous value: -"The inline help text for the field"New value: +"The inline help text for the field. Recommended, but not required -- omit it, or pass '' or null, if the user asked for no help text."

changedInput schema / required

Previous value: -[
-  "sObject",
-  "fieldName",
-  "fieldType",
-  "label",
-  "description",
-  "inlineHelpText"
-]New value: +[
+  "sObject",
+  "fieldName",
+  "fieldType",
+  "label"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "appliedMetadata": {
+      "additionalProperties": true,
+      "description": "The CustomField metadata that was actually sent to Salesforce, including any values the server filled in (e.g. defaulted or 'length'-alias-derived precision/scale). Use this to verify the field was created exactly as intended.",
+      "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 / properties / properties / 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 readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is known. The description adds nothing beyond that: no mention that this mutates org metadata, that re-running with the same fieldName will fail rather than update (non-idempotent), that changes may take time to propagate, or that FLS defaults apply org-wide. With a mutation tool of this complexity, that is a thin contribution.

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, and the purpose is stated immediately. It is efficiently sized, though the brevity is partly the source of the missing context rather than a deliberate trade-off.

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 a 12-parameter tool with nested objects, enum-constrained types, and field-type-dependent properties, one sentence is not enough — an agent has no way to know what to put in 'properties' for, say, a Picklist vs a Lookup. The output schema covers return values, but the invocation-side complexity is unaddressed.

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 all 12 parameters — including the enum for fieldType and FLS settings — are already documented in structured fields. The description adds no semantics about the critical 'properties' map, whose type-dependent requirements it leaves entirely to an unspecified 'instructions'. Baseline 3 applies.

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 field for an sObject in Salesforce'), which is clear on its own. It does not name the obvious sibling sobject_field_update or explain the distinction, so an agent must infer the create-vs-modify boundary.

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 sobject_field_update, metadata_create, or value_set_create, and no prerequisites (permissions, whether the sObject must exist, whether the field type dictates extra properties) are mentioned. The only usage signal comes from the name and annotations.

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?