@browserstack/mcp-server 2.3.0-beta.8 → 2.3.0-beta.9

package/capability/devicecontrol.capability-index.json

@@ -3,6 +3,7 @@
  "version": "1.0",
  "build_id": "8445466_2026-10-19T06:53:46Z",
  "devicecontrol": {
+  "title": "Device Control (Automate)",
   "summary": "Device control: drive a real desktop or mobile browser page by page. The account side lists every operating system, browser and version combination available, reports parallel-session capacity, and keeps each session's record \u2014 status, shareable link, video, and console, network and profiling logs \u2014 after the browser is released. The session side opens a browser on a chosen combination and drives it: navigate, go back and forward, reload, find elements by CSS or XPath, click, type, clear, screenshot the viewport, resize the window, and move between tabs and iframes. Web pages are RUN here \u2014 unlike Test Management, which authors cases, and Test Reporting, which records results pushed in from a runner. Mobile APPS are not here: those are mobile device control, which drives an installed app rather than a browser. Scrolling is done with scroll_to_element or scroll_page, there is no capability that waits, and element ids go stale as soon as the page navigates or re-renders. A session holds a browser until it is ended.",
   "routing_terms": [
    "automate",
@@ -25,7 +26,6 @@
    "scroll",
    "iframe",
    "tab",
-   "cookie",
    "screenshot",
    "console logs",
    "network logs",
@@ -843,7 +843,7 @@
     "intent": "Type into a field \u2014 use this to fill a search box, a login form or any editable input.",
     "guidance": [
      "APPENDS to whatever the field already holds. Call clear_element first to replace the value rather than adding to it.",
-     "Read the result back with get_element_property on \"value\": a field's current contents are a property, not text.",
+     "Read the result back with get_element_property on \"value\": a field's current contents are a property, not text. On Safari for iOS, where property reads answer 405, use get_element_attribute with name value instead.",
      "A \\n at the end submits the form on a desktop browser and on Chrome for Android, and is quicker than finding the submit button. IT DOES NOT SUBMIT ON SAFARI FOR iOS \u2014 the text lands in the field and the page stays where it is, whether the newline is sent with the text or on its own. There, click the form's submit button with click_element \u2014 scroll_to_element first if it sits below the fold.",
      "The element must be editable; typing into anything else answers \"element not interactable\".",
      "A site's own autocomplete or dropdown may swallow the keystrokes and require a click on a suggestion instead."
@@ -895,8 +895,9 @@
     "entity": "browser_session",
     "intent": "Empty an input \u2014 use this before typing, since send_keys adds to what is already there.",
     "guidance": [
+     "WORKS ON EVERY BROWSER: desktop Chrome, Chrome for Android and Safari on iPhone all answer 200 and leave the field empty; typing afterwards starts from nothing.",
      "Takes no parameters of its own.",
-     "Confirm with get_element_property on \"value\", which reads empty afterwards.",
+     "Confirm with get_element_property on \"value\", which reads empty afterwards \u2014 on Safari for iOS, where property reads answer 405, use get_element_attribute with name value instead. Measured empty after clearing on desktop Chrome, Chrome for Android and Safari on iPhone.",
      "Clearing also fires the page's own change handlers, so a form may revalidate and show an error about the now-empty field.",
      "The element must be editable; anything else answers \"invalid element state\"."
     ],
@@ -981,6 +982,7 @@
     "entity": "browser_session",
     "intent": "Read a live DOM property of an element \u2014 use this for what a field currently holds, or whether a box is checked right now.",
     "guidance": [
+     "NOT ON SAFARI FOR iOS: the driver there answers 405 \"unknown method\" to every property read. On an iPhone or iPad read get_element_attribute with name value instead, which returns what the field holds right now; on desktop browsers and Chrome for Android this is the live view and the attribute is the markup.",
      "THIS IS THE ONE THAT READS A FIELD'S CURRENT VALUE. The \"value\" attribute is the markup's initial value rather than what is in the box now, and an input carries no text.",
      "Useful names: value, checked, selected, disabled, innerText, href.",
      "A property the element does not have comes back null, not an error."
@@ -1030,7 +1032,7 @@
     "entity": "browser_session",
     "intent": "Read an HTML attribute of an element \u2014 use this for ids, classes, data- attributes and link targets as the markup declares them.",
     "guidance": [
-     "This is the attribute as written in the HTML, which is NOT what a field currently holds: for that, use get_element_property on \"value\".",
+     "On desktop browsers and Chrome for Android this is the attribute as written in the HTML, which is NOT what a field currently holds: for that, use get_element_property on \"value\". On Safari for iOS it is the other way round \u2014 get_element_property answers 405 there, and this call with name value returns what the field holds right now.",
      "An attribute the element does not carry comes back null rather than an error, so null means absent, not empty.",
      "An attribute a script has changed may still read as the original markup; the property is the live view."
     ],