Skip to main content
Glama
aaron-pienza

Salesforce MCP Server

by aaron-pienza

salesforce_rest_api

Execute direct REST API calls to Salesforce endpoints for reports, composite, files, approvals, and custom APIs, expanding beyond dedicated tool coverage.

Instructions

Make direct REST API calls to any Salesforce REST endpoint. This is a powerful passthrough tool that gives access to the full Salesforce REST API surface — including endpoints not covered by other tools.

Use this for any Salesforce REST API that doesn't have a dedicated tool, such as:

  • Reports and Dashboards API: GET /analytics/reports/{reportId}

  • Composite API: POST /composite

  • Files and ContentDocument: GET /sobjects/ContentDocument/{id}/VersionData

  • Approval Processes: POST /process/approvals

  • Limits and Usage: GET /limits

  • Tabs and Themes: GET /tabs, GET /theme

  • Quick Actions: GET /sobjects/{object}/quickActions

  • Any custom REST endpoint

The endpoint path is relative to /services/data/vXX.0/ (the API version prefix is added automatically).

Examples:

  1. Get org limits:

    • method: "GET"

    • endpoint: "/limits"

  2. Run a report:

    • method: "GET"

    • endpoint: "/analytics/reports/00O5e000004XXXXEAA"

  3. Composite request (multiple operations in one call):

    • method: "POST"

    • endpoint: "/composite"

    • body: { "allOrNone": true, "compositeRequest": [...] }

  4. Get file content:

    • method: "GET"

    • endpoint: "/sobjects/ContentVersion/068XXXXXXXXXXXXXXX/VersionData"

  5. Call a custom REST endpoint:

    • method: "GET"

    • endpoint: "/my-custom-endpoint"

    • rawPath: true

  6. Use a specific API version:

    • method: "GET"

    • endpoint: "/limits"

    • apiVersion: "59.0"

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
methodYesHTTP method: GET, POST, PATCH, PUT, or DELETE
endpointYesREST API endpoint path relative to /services/data/vXX.0/ (e.g., '/limits', '/analytics/reports/{id}'). If rawPath is true, this is the full path from root (e.g., '/services/apexrest/my-endpoint').
bodyNoRequest body for POST, PATCH, and PUT requests. Will be serialized as JSON.
queryParametersNoURL query parameters as key-value pairs (e.g., { "includeDetails": "true" })
apiVersionNoOverride the Salesforce API version (e.g., '59.0', '60.0'). Defaults to the connection's API version.
rawPathNoIf true, the endpoint is treated as a full absolute path from the instance root (e.g., '/services/apexrest/MyEndpoint') instead of being prefixed with /services/data/vXX.0/. Default: false.
Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does not mention potential side effects (e.g., mutations from POST/PUT/DELETE), authentication requirements, rate limits, or other important behaviors. This is a significant gap for a generic passthrough tool.

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?

The description is well-structured with a clear opening statement, numbered examples, and bullet points. While it is somewhat lengthy, each section adds value. It is appropriately front-loaded with the main purpose.

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?

Given the complexity (6 parameters, no output schema, many sibling tools), the description provides extensive examples and clarifies endpoint construction. It covers key usage scenarios comprehensively, though it lacks information on response format and error handling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already describes all 6 parameters with 100% coverage. The description adds value by explaining relative paths, rawPath behavior, and providing concrete examples for parameters like apiVersion and rawPath, going beyond the schema definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Make direct REST API calls to any Salesforce REST endpoint.' It differentiates from siblings by noting it covers endpoints not handled by other tools, and provides numerous examples of specific APIs.

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?

The description explicitly instructs to use this tool for any Salesforce REST API without a dedicated tool, and lists many such APIs. However, it does not explicitly state when not to use it (e.g., preferring dedicated tools when available), though this is implied.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aaron-pienza/mcp-server-salesforce'

If you have feedback or need assistance with the MCP directory API, please join our Discord server