Skip to main content
Glama

connect_salesforce

Connect to a Salesforce org by providing Connected App credentials, username, password, and login URL. Enables Salesforce access for the session.

Instructions

Connect to a Salesforce org in one step.

WHEN TO CALL: At the start of any session that needs Salesforce access, or when get_config shows salesforce.configured = false.

HOW TO ASK THE USER: "To connect to Salesforce I need: 1. Connected App consumer key (client ID) 2. Connected App consumer secret (client secret) 3. Your Salesforce username 4. Your Salesforce password 5. Your security token (optional — only needed if your IP is not allowlisted) 6. Login URL — use https://test.salesforce.com for sandboxes, otherwise leave default

 To get a Connected App:
   Salesforce Setup → App Manager → New Connected App
   Enable OAuth, add 'api' and 'refresh_token' scopes

 These are held in memory for this session only — never stored or logged."

After calling this tool, confirm the connection and proceed with the user's request.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
client_idYesConnected App consumer key
client_secretYesConnected App consumer secret
usernameYesSalesforce username (email format)
passwordYesSalesforce password
security_tokenNoSecurity token — leave blank if IP is allowlisted
login_urlNohttps://login.salesforce.com for production, https://test.salesforce.com for sandboxeshttps://login.salesforce.com
Behavior4/5

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

Discloses that credentials are held in memory only, never stored or logged, and explains OAuth prerequisites. No annotation provided, so description carries the burden well. Minor omission on error behavior.

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?

Well-structured with sections for when-to-call and how-to-ask. Slightly verbose but each part earns its place. Could be trimmed, but still clear.

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?

No output schema, but description does not explain what the tool returns (e.g., success confirmation). Lacks information on rate limits or failure modes. Adequate but has gaps.

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?

Schema coverage is 100%, baseline 3. The 'HOW TO ASK THE USER' section adds detailed instructions for obtaining each parameter (e.g., Connected App setup), going beyond schema descriptions.

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 'Connect to a Salesforce org in one step,' which is a specific verb+resource. The name and content distinguish it from sibling tools like connect_jira and connect_servicenow.

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?

Explicit 'WHEN TO CALL' section provides clear context: at session start or when get_config shows salesforce.configured = false. Does not explicitly state when not to use, but the context suffices.

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/pinnintisagarSB/ServiceNow-Dev-MCP'

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