Skip to main content
Glama

Scroll to an element

well_browser_scroll_to

Scroll the page until the element of the ref is in view. It acts in the Well tab group of the caller's own Chrome, picked with well_select_browser (or the only one connected). Refs come from well_browser_read_page or well_browser_find and go stale when the page changes: read again then.

Input Schema

NameRequiredDescriptionDefault
tab_idNoThe tab, as tabs_context lists it (tab-N). Default: the active tab of the Well group.
targetYesThe element to act on: {"type":"ref","ref":"ref_3"} from well_browser_read_page or well_browser_find.
workspace_idNoTarget workspace. Omit when the token authorizes one workspace. Required when it authorizes several — a write lands in exactly one workspace and this call would not say which.
conversation_idNoThe conversation id returned by the previous Well result, in its meta under well/conversation_id, in its structuredContent, or in its JSON text block. Pass it back on every call in the same conversation, including a call a card makes, so the chosen workspace and the earlier answers still apply. It decides the conversation on its own: nothing the host states about the session replaces it. Omit it only on the first call of a conversation.
idempotency_keyNoOptional client-supplied key. A retried write with the same key returns the original result instead of re-applying the operation.
workspace_scopeNoRestrict this call to the family: the token's primary workspace plus the company workspaces under it that you are a member of. Unrelated authorized workspaces drop out of the read; row reads merge across the family, while a per-workspace figure still reports exactly one workspace.

Output Schema

NameRequiredDescriptionDefault
tabsNo
textNo
errorNo
notesNo
statusNo
successYes
state_changesNo
conversation_idNoThe conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.
newly_connectedNoTools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: "<name> is connected.". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.
conversation_id_noteNoPresent only when the server opened a fresh lane, stating that no choice recorded earlier was read.
conversation_id_sourceNoWhere the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "conversation_id": {
      +      "description": "The conversation this result belongs to. Pass it back as the conversation_id argument on every later Well call in the same conversation.",
      +      "type": "string"
      +    },
      +    "conversation_id_note": {
      +      "description": "Present only when the server opened a fresh lane, stating that no choice recorded earlier was read.",
      +      "type": "string"
      +    },
      +    "conversation_id_source": {
      +      "description": "Where the conversation id came from: the host's own request meta, the caller's argument, or a fresh lane the server opened.",
      +      "enum": [
      +        "host_meta",
      +        "argument",
      +        "minted"
      +      ],
      +      "type": "string"
      +    },
      +    "error": {
      +      "type": "string"
      +    },
      +    "newly_connected": {
      +      "description": "Tools that connected to this workspace since the last result and that no session was told about yet, oldest first. Present only when at least one tool is new. The connected-line rule says when to tell an entry; when it does, one line per entry, in the person's language: \"<name> is connected.\". Never fold several entries into one sentence. Each entry comes back once, on one result only: never repeat its line later.",
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "name": {
      +            "type": "string"
      +          },
      +          "service_id": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "name",
      +          "service_id"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "notes": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "state_changes": {
      +      "items": {
      +        "oneOf": [
      +          {
      +            "additionalProperties": false,
      +            "properties": {
      +              "tab_id": {
      +                "maxLength": 4096,
      +                "minLength": 1,
      +                "type": "string"
      +              },
      +              "type": {
      +                "const": "tab_opened",
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "type",
      +              "tab_id"
      +            ],
      +            "type": "object"
      +          },
      +          {
      +            "additionalProperties": false,
      +            "properties": {
      +              "download_id": {
      +                "minLength": 1,
      +                "type": "string"
      +              },
      +              "type": {
      +                "const": "download_started",
      +                "type": "string"
      +              },
      +              "url": {
      +                "maxLength": 4096,
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "type",
      +              "download_id",
      +              "url"
      +            ],
      +            "type": "object"
      +          },
      +          {
      +            "additionalProperties": false,
      +            "properties": {
      +              "download_id": {
      +                "minLength": 1,
      +                "type": "string"
      +              },
      +              "path": {
      +                "maxLength": 4096,
      +                "type": "string"
      +              },
      +              "size_bytes": {
      +                "maximum": 9007199254740991,
      +                "minimum": 0,
      +                "type": "integer"
      +              },
      +              "type": {
      +                "const": "download_completed",
      +                "type": "string"
      +              },
      +              "url": {
      +                "maxLength": 4096,
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "type",
      +              "download_id",
      +              "url"
      +            ],
      +            "type": "object"
      +          },
      +          {
      +            "additionalProperties": false,
      +            "properties": {
      +              "download_id": {
      +                "minLength": 1,
      +                "type": "string"
      +              },
      +              "error": {
      +                "maxLength": 4096,
      +                "type": "string"
      +              },
      +              "type": {
      +                "const": "download_failed",
      +                "type": "string"
      +              },
      +              "url": {
      +                "maxLength": 4096,
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "type",
      +              "download_id",
      +              "url"
      +            ],
      +            "type": "object"
      +          }
      +        ]
      +      },
      +      "type": "array"
      +    },
      +    "status": {
      +      "enum": [
      +        "ok",
      +        "failed"
      +      ],
      +      "type": "string"
      +    },
      +    "success": {
      +      "type": "boolean"
      +    },
      +    "tabs": {
      +      "items": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "active": {
      +            "type": "boolean"
      +          },
      +          "tab_id": {
      +            "minLength": 1,
      +            "type": "string"
      +          },
      +          "title": {
      +            "maxLength": 4096,
      +            "type": "string"
      +          },
      +          "url": {
      +            "maxLength": 4096,
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "tab_id",
      +          "title",
      +          "url"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "text": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "success"
      +  ],
      +  "type": "object"
      +}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and openWorldHint=true, and the description adds context beyond them: the operation targets the caller's own Chrome tab group, requires a prior browser selection, and that refs invalidate on page change (a real failure mode with a prescribed remedy). It does not say what happens when the ref is no longer present or whether it retries/waits, which keeps it at 4. Nothing contradicts the readOnlyHint=false annotation, since scrolling does mutate page state.

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?

Three short sentences, front-loaded with the action, then environment scoping, then the ref lifecycle hazard. Every sentence carries distinct information an agent needs before calling; nothing is redundant with the title or annotations.

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?

An output schema exists, so return values need not be explained, and the rich schema covers the workspace/conversation plumbing. What remains is behavioural: element-not-found handling, whether the scroll waits for loading content, and how it relates to well_browser_wait — minor gaps for a six-parameter tool whose remaining surface is well documented.

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 description coverage is 100%, so all six parameters (tab_id, target, workspace_id, conversation_id, idempotency_key, workspace_scope) are already documented in the schema, and the baseline is 3. The description adds one piece of genuine meaning beyond the schema — that refs go stale on page change and must be re-read — but says nothing additional about tab selection defaults or workspace scoping.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and precise mechanism: 'Scroll the page until the element of the ref is in view.' The target is unambiguous (a ref-based element), and it names the tools that produce refs (well_browser_read_page, well_browser_find), which implicitly separates it from the clicking/typing siblings. It stops short of explicitly contrasting itself with siblings like well_browser_wait, which is why it isn't a 5.

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?

Gives the prerequisite chain clearly: the action occurs in the Well tab group chosen via well_select_browser (or the only connected one), and refs must originate from well_browser_read_page or well_browser_find. It adds a concrete recovery rule — 'read again then' when refs go stale. No explicit when-not-to-use or comparison to well_browser_wait, so not a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources