Skip to main content
Glama

set_value

Writes text or selects options in editable UI elements such as text fields and combo boxes using the platform's native API. Optionally replaces existing content.

Instructions

Set the value of an editable element.

Calls the platform's native value-setting API.  Behaviour depends
on the target widget:
  * Text fields / text areas: writes the text.
  * Combo boxes / dropdowns / <select>: picks the option whose
    label or value matches *value*.  Prefer this over clicking
    the dropdown and then clicking a popup item — picking by name
    is one atomic call and avoids popup-click failures on some
    toolkits.
  * Other editable widgets: whatever their value interface accepts.

Args:
    element_id: The element ID (a text field, combo box, etc.).
    value: The text or option label to set.
    replace: If true, clear the field first and replace all content.
             If false (default), insert at the current cursor position.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
element_idYes
valueYes
replaceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so the description fully bears the transparency burden. It discloses widget-dependent behavior, the atomic nature for combo boxes, and the replace parameter effect. Missing error conditions or side effects, but still thorough.

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?

The description is well-structured with a brief overview, bullet-pointed widget behaviors, and parameter details. Every sentence is informative and necessary; no fluff.

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 all parameters, widget-behavior breakdown, and usage hints. The presence of an output schema (not shown) offsets the lack of return-value explanation. Minor gap: no mention of error handling or edge cases.

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 0%, but the description explains each parameter thoroughly: element_id as the widget, value as text or option label, and replace with clear semantics (clear+replace vs insert). This adds rich meaning beyond the schema.

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 sets the value of an editable element and lists specific widget behaviors (text fields, combo boxes, etc.), distinguishing it from siblings like type_text and click by emphasizing atomic value-setting via native API.

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?

Provides explicit usage guidance, e.g., preferring set_value over clicking for combo boxes to avoid popup failures. Though it does not list exclusions, the context is clear for when to use the tool.

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/Touchpoint-Labs/Touchpoint'

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