Cirra AI Salesforce Admin MCP Server

link_build

Read-onlyIdempotent

Build Salesforce links for setup pages. Always use this tool when user requests a setup page link

Input Schema

Name	Required	Description
`type`	Yes	The type of the link to build
`sf_user`	No	(optional) Salesforce username to identify the connection to use. If not provided, the default connection will be used
`setupConfig`	No	Used with `setup` types. Describes the type of setup page to build link for
`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.

Output Schema

Name	Required	Description
`result`	No	The built link as an object with href (the setup page URL) and label (display text), or null when no link applies (e.g. delete operations or when the link could not be built)
`message`	Yes	Human-readable summary of the result
`success`	Yes	Whether the operation succeeded
`warning`	No	Optional warning about the current connection or result

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 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 / properties / setupConfig / properties / artifactNameOrId / description

Previous value: -"The name or ID of artifact. For example a class name, class ID, page layout name, validation rule name, value set name, trigger name, flow name, username, user ID or flow name"New value: +"The name or ID of artifact. For example a class name, class ID, page layout name, validation rule name, value set name, trigger name, flow name, username, user ID, or ApexLog Id (prefix 07L)"

changedInput schema / properties / setupConfig / properties / type / enum

Previous value: -[
-  "Object",
-  "Field",
-  "Page Layout",
-  "Record Type",
-  "Apex Trigger",
-  "Validation Rule",
-  "Value Set",
-  "Business Process",
-  "Flow Trigger",
-  "Permission Set",
-  "Profile",
-  "User",
-  "Flow",
-  "Class",
-  "Trigger",
-  "Group",
-  "Queue",
-  "Role",
-  "Email Template",
-  "Report",
-  "Dashboard",
-  "Workflow Rule",
-  "Email Alert",
-  "Field Update",
-  "Outbound Message",
-  "Workflow Task"
-]New value: +[
+  "Object",
+  "Field",
+  "Page Layout",
+  "Record Type",
+  "Apex Trigger",
+  "Validation Rule",
+  "Value Set",
+  "Business Process",
+  "Flow Trigger",
+  "Permission Set",
+  "Profile",
+  "User",
+  "Flow",
+  "Class",
+  "Apex Debug Log",
+  "Trigger",
+  "Group",
+  "Queue",
+  "Role",
+  "Email Template",
+  "Report",
+  "Dashboard",
+  "Workflow Rule",
+  "Email Alert",
+  "Field Update",
+  "Outbound Message",
+  "Workflow Task"
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "message": {
+      "description": "Human-readable summary of the result",
+      "type": "string"
+    },
+    "result": {
+      "description": "The built link as an object with href (the setup page URL) and label (display text), or null when no link applies (e.g. delete operations or when the link could not be built)"
+    },
+    "success": {
+      "description": "Whether the operation succeeded",
+      "type": "boolean"
+    },
+    "warning": {
+      "description": "Optional warning about the current connection or result",
+      "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

Changed1 schema field changedMar 18, 2026

changedInput schema / properties / setupConfig / properties / type / enum

Previous value: -[
-  "Object",
-  "Field",
-  "Page Layout",
-  "Lightning Record Page",
-  "Button Link or Action",
-  "Link",
-  "Action",
-  "Record Type",
-  "Apex Trigger",
-  "Validation Rule",
-  "Value Set",
-  "Business Process",
-  "Flow Trigger",
-  "Permission Set",
-  "Profile",
-  "User",
-  "Flow",
-  "Class",
-  "Trigger",
-  "Group",
-  "Queue",
-  "Role",
-  "Email Template"
-]New value: +[
+  "Object",
+  "Field",
+  "Page Layout",
+  "Record Type",
+  "Apex Trigger",
+  "Validation Rule",
+  "Value Set",
+  "Business Process",
+  "Flow Trigger",
+  "Permission Set",
+  "Profile",
+  "User",
+  "Flow",
+  "Class",
+  "Trigger",
+  "Group",
+  "Queue",
+  "Role",
+  "Email Template",
+  "Report",
+  "Dashboard",
+  "Workflow Rule",
+  "Email Alert",
+  "Field Update",
+  "Outbound Message",
+  "Workflow Task"
+]

AddedFeb 26, 2026
RemovedFeb 26, 2026
First observedJan 31, 2026

TDQS

B3.4/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds nothing beyond that — no indication of what a returned link looks like, whether it is a URL string or an object, or how incomplete setupConfig affects the result.

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?

Two tight sentences with the purpose front-loaded and no filler. The second sentence is somewhat imperative/redundant with the first but still earns its place as a routing rule.

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?

With an output schema and rich annotations, the description needn't explain return values or safety. However, for a tool with a nested setupConfig object and connection-selection parameters, it says nothing about the fact that a useful link requires specifying an artifact type and name, leaving the agent to infer this entirely from the schema.

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 the nested setupConfig fields (type, sObjectNameOrId, artifactNameOrId) are individually documented, so the baseline of 3 applies. The description mentions no parameter at all, not even the required type='setup' or how setupConfig changes the output link.

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: 'Build Salesforce links for setup pages.' An agent can immediately tell this generates URLs rather than manipulating metadata. No sibling tool produces links, so differentiation is implicit rather than stated.

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?

'Always use this tool when user requests a setup page link' gives a clear triggering condition. It lacks anything on when not to use it or on what happens if setupConfig is omitted, but the positive routing rule is unambiguous.

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?