Skip to main content
Glama
Sign In
Salesforce MCP Server

Salesforce MCP Server

by LokiMCPUniverse
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

salesforce_run_report

Run a Salesforce analytics report by ID, with optional filters to retrieve the report's data.

Instructions

Run a Salesforce analytics report.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "report_id": "<report_id>"
    },
    "name": "salesforce_run_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgNo
filtersNo
report_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the operation without mentioning side effects, authorization requirements, output format, or error behavior. This is insufficient for a tool that executes a report, which likely has side effects like runtime limits.

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

Conciseness3/5

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

The description is concise at one sentence, but it is under-specified. It is not a tautology, yet it offers little structured information. While it is front-loaded, it does not earn its place due to minimal content.

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?

Even though an output schema exists, the description is too thin to provide complete context for a 3-parameter tool. It does not explain the relationship between org, filters, and report_id, nor does it cover potential pitfalls like filter syntax or org selection.

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

Parameters1/5

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

The description provides no information about the three parameters (org, filters, report_id). Schema description coverage is 0%, so the agent receives no semantic guidance beyond the parameter names and types, which is inadequate for constructing a correct invocation.

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?

The description uses a specific verb 'Run' and identifies the resource as 'a Salesforce analytics report,' which clearly distinguishes it from sibling tools like salesforce_query (which runs SOQL) and salesforce_search. However, it lacks scope details such as whether it returns data or just executes.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, typical use cases, or when to prefer salesforce_query or salesforce_execute_apex.

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

Deploy Server

Other Tools