Skip to main content
Glama
Deviank88

Salesforce MCP UI Automation

by Deviank88

select

Select an option from a native dropdown field by specifying a CSS selector, option label, or value. Ideal for automating form selections in Salesforce.

Instructions

Select an option in a native select field by selector or label.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
valueNo
labelNo
selectorNo
option_labelNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits such as whether the tool waits for page updates, error handling for missing elements, or side effects.

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 (one sentence) but at the cost of missing important details, making it efficient yet insufficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the presence of 4 parameters, no annotations, and an output schema, the description is severely lacking in completeness, providing no information on return values, prerequisites, or error conditions.

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

Parameters2/5

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

Schema description coverage is 0%, and the description only weakly hints at parameters (by selector or label), without explaining the distinct roles of value, label, selector, and option_label.

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 selects an option in a native select field using a selector or label, which distinguishes it from sibling tools like click or fill.

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, nor any conditions for use or exclusions.

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/Deviank88/Salesforce-MCP-UI-Automation'

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