Cirra AI Salesforce Admin MCP Server

report_run

Read-onlyIdempotent

Execute a Salesforce report by ID and return its results, with optional filters and format overrides

Input Schema

Name	Required	Description
`sf_user`	No	(optional) Salesforce username to identify the connection to use. Omit this to use the current default connection.
`pageSize`	No	(optional) Maximum number of records to return per page when the response requires pagination, including the first page. If omitted, the first page is a short preview and later pages use an automatically calculated size.
`reportId`	Yes	The ID of the report to execute (15 or 18 character Salesforce ID)
`maxRecords`	Yes	Maximum number of records to return. Defaults to 2000
`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.
`includeDetails`	Yes	Whether to include detailed row data in the response. Defaults to true
`reportMetadata`	Yes	Optional report metadata to override report configuration

Output Schema

Name	Required	Description	Default
`report`	No
`message`	Yes
`results`	No
`success`	Yes
`warning`	No
`errorCode`	No
`errorCount`	No
`resultCount`	No
`artifactType`	No
`requestCount`	No
`skippedCount`	No
`successCount`	No
`artifactCategory`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 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 / pageSize / description

Previous value: -"(optional) Maximum number of records to return per page when the response requires pagination. If omitted, page size is calculated automatically."New value: +"(optional) Maximum number of records to return per page when the response requires pagination, including the first page. If omitted, the first page is a short preview and later pages use an automatically calculated size."

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

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "artifactCategory": {
+      "type": "string"
+    },
+    "artifactType": {
+      "type": "string"
+    },
+    "errorCode": {
+      "type": "string"
+    },
+    "errorCount": {
+      "type": "number"
+    },
+    "message": {
+      "type": "string"
+    },
+    "report": {
+      "additionalProperties": true,
+      "properties": {},
+      "type": "object"
+    },
+    "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

Changed1 schema field changedMar 18, 2026

addedInput schema / properties / pageSize

Added value: +{
+  "description": "(optional) Maximum number of records to return per page when the response requires pagination. If omitted, page size is calculated automatically.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

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

TDQS

B3.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that results are returned and filters/format can be overridden, but says nothing about pagination behavior (a real concern given pageSize and maxRecords) or the connection/context selection requirement.

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

Conciseness5/5

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

A single front-loaded sentence that names the action, the identifier, the output, and the optional knobs. Nothing is redundant or buried.

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?

An output schema exists, so return values needn't be explained. However, for a tool with 8 parameters, nested objects, and a connection-selection rule where a call with neither context_handle nor cirra_ai_team + sf_user is refused, the description omits that prerequisite and the pagination semantics entirely.

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 8 parameters including the nested reportFilters and reportFormat. The description only echoes "optional filters and format overrides" and adds no syntax, defaults, or semantics beyond what the schema provides.

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: "Execute a Salesforce report by ID and return its results," plus the scope of optional filters and format overrides. An agent can distinguish this from the query siblings (soql_query, bulk_query) by the saved-report framing, though no sibling is named explicitly.

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 explicit when-to-use guidance and no alternatives are named, even though soql_query, bulk_query, and tooling_api_query sit in the same family. The agent must infer that this is for pre-built reports rather than ad-hoc queries.

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?