Skip to main content
Glama

select_option

Select an option from a native or custom dropdown by value, label, or index. Automatically detects the element type and returns the resulting selection. Supports targeting the Nth match for identical elements.

Instructions

Select an option from a native or a custom dropdown (Radix/shadcn combobox), auto-detecting which. Choose by value, label, or index. Returns {success} and the resulting selection. For custom dropdowns it opens the menu and clicks the matching option — use this rather than click+click. When a page has several attribute-less elements, pass element_index to target the Nth match of the selector (Playwright '>>' syntax is not supported).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
indexNoOption index to select (0-based)
labelNoOption label text to select
valueNoOption value to select
observeNoWhat to return about the resulting page. 'screenshot' (default): full-page image. 'none': structured result only, no image — cheapest, use through setup steps of a flow. 'map': semantic page map (get_page_map — token-light, best for 'what can I do next?'). 'checks': run_checks_on_session output (a11y/seo/perf/etc.).screenshot
selectorYesCSS selector for the <select> or combobox trigger (plain CSS only — no Playwright '>>' syntax)
session_idYesSession ID
element_indexNoWhich match of 'selector' to target, 0-based (default: 0). Use for the 2nd/3rd attribute-less <select> on a page.
Behavior3/5

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

No annotations provided, so description bears full burden. Discloses auto-detection, menu opening for custom dropdowns, and Playwright syntax limitation. But omits error handling (e.g., option not found), prerequisites (element visible), and safety implications.

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

Conciseness5/5

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

Four sentences with no wasted words. Front-loaded with purpose and method, then key behaviors. Efficient and well-organized.

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 most aspects: how to specify option, targeting multiple elements, observe parameter, and selector limitation. Missing clarifications on exclusive usage of option parameters and detailed return structure. Adequate for a tool with 7 params and no output schema.

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 coverage is 100%, baseline 3. Description adds context for selector (no '>>' syntax) and element_index (use for attribute-less selects). For option parameters, it only restates what schema says, adding minimal value.

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 verb 'select', resource 'option from a native <select> or custom dropdown', and specifies methods: by value, label, or index. Distinguishes from sibling tools like click_element by emphasizing it handles both native and custom dropdowns.

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?

Explicitly says to use this tool rather than click+click for custom dropdowns, and advises using element_index when multiple attribute-less <select> elements exist. However, lacks explicit exclusions or alternatives for other scenarios.

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/segentic-lab/periscope-mcp'

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