Skip to main content
Glama

Salesforce Connector

salesforce_connector
Read-onlyIdempotent

Salesforce CRM read access via the CorpusIQ breadth tier (sourced through Arcade, not a first-party connector). Read-only: search opportunities, leads, contacts; pull pre-joined account 360s; inspect a single opportunity; list tasks; resolve the current user. Pipeline, forecast, deals-at-risk, account-history questions. Writes are intentionally not exposed (default-deny). When the user asks for a visual, trend, comparison, or recap, call chart_render with the numeric values returned by this connector. If the connector result includes a verified chart_provenance token, the same authenticated user may pass it as provenance_token within 15 minutes, on any replica, and map every value to its exact source_path so chart_render preserves verified provenance. Without a valid connector receipt, chart_render labels values as unverified_model_data. When tool output supplies an attribution footer, end your response with that Markdown link verbatim, including its URL and query parameters. Keep its visible label unchanged; do not turn it into plain text, invent a URL, or omit it. Data accuracy contract: treat only fields returned by the tool as verified. Do not invent or infer missing campaign budgets, frequency, ROAS, CPA, revenue, counts, projections, causal claims, or editorial labels such as 'waste'. Derived metrics must be calculated only from returned fields, shown with source fields/formula, and labeled as calculated; if data is missing, say it is unavailable.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYessalesforce_get_account_by_id: Gets the account with related info: contacts, leads, notes, calls, opportunities, tasks, emails, and events (up to 10 it | salesforce_get_account_by_keywords: Searches for accounts in Salesforce and returns them with related info: contacts, leads, notes, calls, opportunities, ta | salesforce_get_opportunity_by_id: Gets a single opportunity with enriched related data: contact roles, line items, open tasks, and recent notes. [Breadth- | salesforce_list_my_tasks: Lists tasks assigned to you in Salesforce with optional filters. Excludes call logs and email activities — only shows a | salesforce_search_contacts: Searches for contacts in Salesforce with optional filters. At least one filter (query, account_id, or title) must be pr | salesforce_search_leads: Searches for leads in Salesforce with optional filters. Always excludes already-converted leads. Use owner='me' (defaul | salesforce_search_opportunities: Searches for opportunities (deals) in Salesforce with optional filters. Returns a paginated list of opportunities with | salesforce_whoami: Get information about the currently authenticated Salesforce user. This is typically the first tool called to establish
paramsNoAction-specific parameters. salesforce_get_account_by_id: {account_id: string} | salesforce_get_account_by_keywords: {query: string, limit?: integer, page?: integer} | salesforce_get_opportunity_by_id: {opportunity_id: string} | salesforce_list_my_tasks: {status?: string, due_date_from?: string, due_date_to?: string, overdue_only?: boolean, account_or_opportunity_id?: string, limit?: integer, page?: integer} | salesforce_search_contacts: {query?: string, account_id?: string, title?: string, limit?: integer, page?: integer} | salesforce_search_leads: {query?: string, status?: string, owner?: string, lead_source?: string, created_after?: string, limit?: integer, page?: integer} | salesforce_search_opportunities: {query?: string, stage?: string, close_date_from?: string, close_date_to?: string, owner?: string, min_amount?: number, limit?: integer, page?: integer} | salesforce_whoami: none

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, it discloses the default-deny write posture, the 15-minute cross-replica provenance_token receipt semantics, the unverified_model_data fallback, mandatory attribution footer handling, and a data accuracy contract. This is unusually rich behavioral context that the annotations alone do not provide.

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 purpose is front-loaded in the first sentence, which is good, but the description then sprawls across multiple concerns (provenance tokens, footer verbatim rules, accuracy contract) that read like policy boilerplate rather than tool-selection guidance. Several sentences do not help the agent decide or invoke.

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?

For an eight-action connector with no output schema, the description conveys the shape of returns (pre-joined account 360s, paginated opportunity lists) and the key behavioral contracts. It is largely complete, though return-value specifics for each action remain thin.

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 action enum plus per-action params are fully documented in the schema, so the baseline is 3. The prose description adds no parameter-level syntax, format, or default information beyond what the schema already carries.

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 names specific verbs and resources: search opportunities/leads/contacts, pull pre-joined account 360s, inspect a single opportunity, list tasks, resolve the current user. It is highly specific about what the connector does, but it never distinguishes itself from the sibling crm_connector, leaving the agent to guess when one is preferred over the other.

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?

It gives clear usage contexts ('Pipeline, forecast, deals-at-risk, account-history questions') and explicitly excludes a whole class of operations ('Writes are intentionally not exposed (default-deny)'). It also routes visual/trend/comparison requests to chart_render. It stops short of naming an alternative connector for those excluded write paths.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources