Skip to main content
Glama
aaronsb

Salesforce MCP Server

search_fields

Find Salesforce field API names by searching field labels, API names, and help text. Returns ranked matches across objects or within a specific object.

Instructions

Find the field(s) that carry a concept, when you know what you want to query but not the API name. Searches every scored field on the discovered objects — not just the promoted ones — across API names, labels, and help text, ranked by match strength. Searches the core objects by default; pass objectName to scope to one, which discovers it on demand. Set includeValues to get the value set for matched picklists, so you can write the WHERE clause without a second lookup. The match is lexical, not semantic: it finds fields whose name, label or help text contains the term, so a concept this org names differently will not surface, and an object that has not been discovered is not searched. Read salesforce://field-catalog/{objectName}/all to browse everything on an object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termYesWhat to look for, matched against field API names, labels, and help text (e.g. "ai", "renewal date", "region")
limitNoMaximum matches to return (default: 25, max: 100)
objectNameNoRestrict the search to one object (e.g. Opportunity). Omit to search all discovered core objects.
includeValuesNoInclude the active value set for matched picklist fields (default: false). Free — the values come from metadata already discovered.
minPopulationPctNoDrop fields populated on fewer than this percent of records (0-100). Omit to include sparsely-populated fields, which is often where custom flags live.
Behavior5/5

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

No annotations provided, so description bears full burden. Fully discloses limitations: lexical match, only discovered objects, and that includeValues is free. No contradictions.

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?

Single paragraph but well-organized with main purpose first. Each sentence adds value. Could be slightly more structured with bullet points, but still concise and clear.

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?

Covers behavior, limitations, and usage context thoroughly. Does not explicitly describe output format, but given no output schema, it mentions ranking. Slightly lacking in output details.

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

Parameters5/5

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

Schema description coverage is 100%, but description adds meaning beyond schema (e.g., default behavior for objectName, cost-free for includeValues, clarification on minPopulationPct).

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?

Clearly states the tool's purpose: finding fields by concept when API name unknown. Describes what is searched (every scored field on discovered objects) and ranking. No sibling tool duplicates this function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use: when you know what to query but not API name. Provides exclusions (lexical not semantic, only discovered objects). Includes alternative for browsing via field-catalog resource.

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/aaronsb/salesforce-cloud'

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