Skip to main content
Glama
dlwjdtn535

mcp-chrome-server

tool_type

Finds an input element, clears existing text, and types specified text into it using CSS or XPath selectors.

Instructions

Type text into an element.

    This tool finds an input element and types the specified text into it.
    It will clear any existing text in the element before typing.
    
    Args:
        selector (str): The selector to find the element
        text (str): The text to type into the element
        by (str, optional): The selector type. Either "css" or "xpath". Defaults to "css"
    
    Returns:
        Dict[str, Any]: A dictionary containing:
            - success (bool): Whether the operation was successful
            - message (str): Status message
    
    Example:
        {"tool": "type", "args": {"selector": "#search-input", "text": "search query"}}
        {"tool": "type", "args": {"selector": "//input[@name='q']", "text": "search", "by": "xpath"}}
    

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
selectorYes
textYes
byNocss
Behavior4/5

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

With no annotations, the description carries full burden. It discloses that it clears existing text, uses default selector type, and returns success/message. Missing details on error handling (e.g., element not found) or preconditions like element visibility.

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 clear sections (short description, args, returns, example). It is concise and front-loaded with the primary action. Every sentence adds value.

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?

Given no output schema, the description explains inputs and return structure adequately. However, it could mention implicit requirements (e.g., element must exist and be interactable) to achieve full completeness.

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 tool description provides complete meaning for each parameter: selector finds the element, text is the input, by specifies css or xpath. This fully compensates for the missing schema descriptions.

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's action: 'Type text into an element.' The verb 'type' and resource 'element' are specific. Among siblings like tool_click and tool_get_text, this tool is uniquely identified for text input.

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?

The description explains the behavior of clearing existing text and defaults to CSS selector. It provides an example for both CSS and XPath. However, it does not explicitly state when not to use this tool or compare it to alternatives like tool_execute_script for complex inputs.

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/dlwjdtn535/mcp-chrome-server'

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