← WebMCP Directory

Tool tree

docs.split.io

Developer ToolsTools verified
Website
This section details Split API. Split API uses resource-oriented URLs, uses status codes to indicate the success or failure of requests and returns JSON from all requests. You can use Split API to…
Explore capabilities

    page: Every page

    search_docsAnswer

    Search the documentation site for Split docs. Returns a list of relevant pages with titles and excerpts.

    View tool JSON
    {
      "name": "search_docs",
      "kind": "answer",
      "impl": "imperative",
      "description": "Search the documentation site for Split docs. Returns a list of relevant pages with titles and excerpts.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "query": {
            "type": "string",
            "description": "Search query string."
          }
        },
        "required": [
          "query"
        ]
      },
      "page": "/reference/introduction"
    }
    navigate_to_pageAction

    Navigate the browser to a specific documentation page by path. Use search_docs first to find candidate paths.

    View tool JSON
    {
      "name": "navigate_to_page",
      "kind": "act",
      "impl": "imperative",
      "description": "Navigate the browser to a specific documentation page by path. Use search_docs first to find candidate paths.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "path": {
            "type": "string",
            "description": "Relative path, e.g. \"/docs/getting-started\" or \"/reference/create-widget\"."
          }
        },
        "required": [
          "path"
        ]
      },
      "page": "/reference/introduction"
    }
    get_current_page_contentAnswer

    Return the current documentation page as markdown so the agent can reason about what the user is currently reading.

    View tool JSON
    {
      "name": "get_current_page_content",
      "kind": "answer",
      "impl": "imperative",
      "description": "Return the current documentation page as markdown so the agent can reason about what the user is currently reading.",
      "inputSchema": {
        "type": "object",
        "properties": {}
      },
      "page": "/reference/introduction"
    }