Cirra AI Salesforce Admin MCP Server

fetch_more

Read-onlyIdempotent

Fetch the next page of a large tool response. Use the nextCursor from _pagination in a previous response. This tool loads data into the context window — prefer the artifact download URL when available.

Input Schema

Name	Required	Description
`cursor`	Yes	Pagination cursor from _pagination.nextCursor
`pageSize`	No	(optional) Number of records to return in this page. If omitted, uses the page size from the original query.
`artifactId`	Yes	Artifact ID from artifactAccess.artifactId
`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
`message`	Yes	Human-readable summary of the result
`success`	Yes	Whether the operation succeeded
`warning`	No	Optional warning about the result
`_pagination`	No	Pagination state for the returned page

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 1, 2026

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

changedInput schema / properties / artifactId / description

Previous value: -"Artifact ID from instructions.artifactId"New value: +"Artifact ID from artifactAccess.artifactId"

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"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "_pagination": {
+      "additionalProperties": true,
+      "description": "Pagination state for the returned page",
+      "properties": {
+        "nextCursor": {
+          "description": "Cursor for the next page; absent when there are no more records",
+          "type": "string"
+        },
+        "returned": {
+          "description": "Number of records returned in this page",
+          "type": "number"
+        },
+        "total": {
+          "description": "Total number of records in the full result set",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "message": {
+      "description": "Human-readable summary of the result",
+      "type": "string"
+    },
+    "success": {
+      "description": "Whether the operation succeeded",
+      "type": "boolean"
+    },
+    "warning": {
+      "description": "Optional warning about the result",
+      "type": "string"
+    }
+  },
+  "required": [
+    "success",
+    "message"
+  ],
+  "type": "object"
+}

AddedMay 8, 2026
RemovedMay 8, 2026

Changed1 schema field changedMar 18, 2026

addedInput schema / properties / pageSize

Added value: +{
+  "description": "(optional) Number of records to return in this page. If omitted, uses the page size from the original query.",
+  "maximum": 9007199254740991,
+  "minimum": -9007199254740991,
+  "type": "integer"
+}

AddedMar 11, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover read-only/idempotent safety, and the description adds the key behavioral trait they can't express: this call consumes context window budget, which is why the artifact URL is preferred. It doesn't mention cursor expiry or failure behavior, keeping it below a 5.

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?

Three short sentences, front-loaded with what it does, then how to use it, then the caution. Every sentence carries distinct, actionable information.

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?

Output schema exists and parameters are fully described, so the description only needs to add the context-cost warning and cursor provenance, both of which it does. Minor gap: no note on what happens with an expired or invalid cursor.

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 coverage is 100%, so all four parameters, including their origins (artifactAccess.artifactId, _pagination.nextCursor, cirra_ai_init context_handle), are already documented. The description restates the cursor source but adds nothing new about parameters.

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: 'Fetch the next page of a large tool response.' It is unambiguous and no sibling tool covers pagination, so confusion risk is low, though it doesn't name a specific alternative sibling.

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?

Gives a clear trigger ('Use the nextCursor from _pagination in a previous response') and points to a preferred alternative ('prefer the artifact download URL when available'). It lacks an explicit 'do not call when...' case, but the routing signal is strong.

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?