Skip to main content
Glama

select_text

Select a substring within an element's text content to format, copy, or replace specific text. Specify the exact text and choose which occurrence to select.

Instructions

Select a substring within an element's text content.

Finds the text within the element and applies a native text
selection over that range.  Useful for formatting, copying,
or replacing specific text within a document or text field.

Args:
    element_id: The element ID containing the text.
    text: The exact substring to select.
    occurrence: Which occurrence to select (1 = first, 2 = second, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
element_idYes
textYes
occurrenceNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It explains that the tool 'applies a native text selection over that range', which is a basic behavioral disclosure. However, it does not mention potential side effects (e.g., triggering events, scrolling, element visibility requirements) or output behavior, limiting transparency.

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?

The description is efficient: a clear one-liner definition, followed by a brief usage context, and a structured Args block. The first sentence front-loads the core purpose. Minor redundancy in 'Finds the text within the element' could be trimmed.

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?

All three parameters are explained, and the output schema (not shown) likely covers return values. The description adequately covers input semantics but lacks details on error conditions or behavior when the text is not found.

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%, and the description adds an Args section explaining each parameter: element_id (the element ID containing the text), text (the exact substring to select), and occurrence (which occurrence to select). This adds significant meaning beyond the schema's titles and defaults.

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 a substring within an element's text content, using specific verb 'select' and resource 'substring within element's text'. It also mentions common use cases (formatting, copying, replacing), making the purpose unambiguous and distinct from siblings like type_text or set_value.

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

Usage Guidelines3/5

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

The description implies when to use the tool (e.g., for formatting, copying, replacing text) but does not explicitly state when not to use it or compare to alternatives. No guidance on prerequisites or context is provided.

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