← WebMCP Directory

Tool tree

w3-digitalbrands.com

Productivity & BusinessTools verified
Website
W3 Digital Brands provides website, web app and digital visibility services.
Explore capabilities

    page: Agentur

    lets_have_confettiAction

    Lets have a celebration! This function will create an effect of a celebration on the page.

    View tool JSON
    {
      "name": "lets_have_confetti",
      "kind": "act",
      "impl": "imperative",
      "description": "Lets have a celebration! This function will create an effect of a celebration on the page.",
      "inputSchema": {
        "type": "object",
        "properties": {}
      },
      "page": "/agentur"
    }
    lets_have_fireworksAction

    Lets have a celebration! This function will create an effect of a celebration on the page.

    View tool JSON
    {
      "name": "lets_have_fireworks",
      "kind": "act",
      "impl": "imperative",
      "description": "Lets have a celebration! This function will create an effect of a celebration on the page.",
      "inputSchema": {
        "type": "object",
        "properties": {}
      },
      "page": "/agentur"
    }
    change_themeAction

    Changes the theme of the page to dark or light.

    View tool JSON
    {
      "name": "change_theme",
      "kind": "act",
      "impl": "imperative",
      "description": "Changes the theme of the page to dark or light.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "theme": {
            "type": "string",
            "description": "The theme to change to"
          }
        }
      },
      "page": "/agentur"
    }
    list_pagesAnswer

    List page slugs derived from the live sitemap.xml (fetched server-side from the configured public site URL). Use slugs with call_page.

    View tool JSON
    {
      "name": "list_pages",
      "kind": "answer",
      "impl": "imperative",
      "description": "List page slugs derived from the live sitemap.xml (fetched server-side from the configured public site URL). Use slugs with call_page.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "limit": {
            "type": "number",
            "description": "Max number of slugs to return (optional; server caps apply)"
          }
        }
      },
      "page": "/agentur"
    }
    call_pageSensitive Action

    Open a published page from the sitemap in the current language. When the user wants the contact form filled, you MUST pass contact_form in the SAME call together with the contact slug (kontakt / contact / etc.)—do not navigate only and skip the form. contact_form fields: name, email, phone, message. When contact_form is included, the form is submitted by default after filling (fill + send in one step). Pass contact_form.submit: false only if the user wants fields filled but not sent. If the user said send/submit, you may omit submit or set submit: true. Alternatively fill_contact_form can be used after navigation (fill only, never submits), but contact_form on call_page is preferred for fill-and-send.

    View tool JSON
    {
      "name": "call_page",
      "kind": "transact",
      "impl": "imperative",
      "description": "Open a published page from the sitemap in the current language. When the user wants the contact form filled, you MUST pass contact_form in the SAME call together with the contact slug (kontakt / contact / etc.)—do not navigate only and skip the form. contact_form fields: name, email, phone, message. When contact_form is included, the form is submitted by default after filling (fill + send in one step). Pass contact_form.submit: false only if the user wants fields filled but not sent. If the user said send/submit, you may omit submit or set submit: true. Alternatively fill_contact_form can be used after navigation (fill only, never submits), but contact_form on call_page is preferred for fill-and-send.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "slug": {
            "type": "string",
            "description": "Storyblok / sitemap page slug (e.g. kontakt, contact, home)"
          },
          "contact_form": {
            "type": "object",
            "description": "If the user provided contact details, include this object on the same call_page as the contact page slug so the form is filled immediately after navigation (preferred over a second tool). Submits after fill unless submit is explicitly false.",
            "properties": {
              "name": {
                "type": "string",
                "description": "Sender full name"
              },
              "email": {
                "type": "string",
                "description": "Sender email"
              },
              "phone": {
                "type": "string",
                "description": "Sender phone (optional)"
              },
              "message": {
                "type": "string",
                "description": "Message body"
              },
              "submit": {
                "type": "boolean",
                "description": "If false, only fills fields—does not send. If true or omitted, submits the form after filling (default: send when contact_form is present)."
              }
            }
          }
        },
        "required": [
          "slug"
        ]
      },
      "page": "/agentur"
    }
    fill_contact_formAction

    Fills the contact form on the current page (name, email, phone, message). This tool NEVER submits the form—use call_page with the contact page slug and contact_form to fill and send (call_page submits by default when contact_form is present; use contact_form.submit: false for fill-only). Sets tool-form-active on the form for WebMCP UI. Prefer contact_form on call_page when navigating and filling in one step.

    View tool JSON
    {
      "name": "fill_contact_form",
      "kind": "act",
      "impl": "imperative",
      "description": "Fills the contact form on the current page (name, email, phone, message). This tool NEVER submits the form—use call_page with the contact page slug and contact_form to fill and send (call_page submits by default when contact_form is present; use contact_form.submit: false for fill-only). Sets tool-form-active on the form for WebMCP UI. Prefer contact_form on call_page when navigating and filling in one step.",
      "inputSchema": {
        "type": "object",
        "properties": {
          "name": {
            "type": "string",
            "description": "Sender full name"
          },
          "email": {
            "type": "string",
            "description": "Sender email"
          },
          "phone": {
            "type": "string",
            "description": "Sender phone (optional)"
          },
          "message": {
            "type": "string",
            "description": "Message body"
          }
        }
      },
      "page": "/agentur"
    }
    scroll_to_contact_formAction

    Scrolls the contact form section into view on the current page (smooth scroll). Use on the contact page when the form is off-screen or before fill_contact_form so the user sees the widget.

    View tool JSON
    {
      "name": "scroll_to_contact_form",
      "kind": "act",
      "impl": "imperative",
      "description": "Scrolls the contact form section into view on the current page (smooth scroll). Use on the contact page when the form is off-screen or before fill_contact_form so the user sees the widget.",
      "inputSchema": {
        "type": "object",
        "properties": {}
      },
      "page": "/agentur"
    }

    page: Websites

    contact_formSensitive Action

    Get in touch with us

    View tool JSON
    {
      "name": "contact_form",
      "kind": "transact",
      "impl": "declarative",
      "description": "Get in touch with us",
      "inputSchema": {
        "type": "object",
        "properties": {
          "_hp": {
            "type": "string"
          },
          "name": {
            "type": "string",
            "description": "Name"
          },
          "email": {
            "type": "string",
            "description": "E-Mail"
          },
          "phone": {
            "type": "string",
            "description": "Telefon"
          },
          "message": {
            "type": "string",
            "description": "Nachricht"
          }
        },
        "required": [
          "name",
          "email",
          "message"
        ]
      },
      "page": "/websites"
    }

    page: Visibility

    contact_formSensitive Action

    Get in touch with us

    View tool JSON
    {
      "name": "contact_form",
      "kind": "transact",
      "impl": "declarative",
      "description": "Get in touch with us",
      "inputSchema": {
        "type": "object",
        "properties": {
          "_hp": {
            "type": "string"
          },
          "name": {
            "type": "string",
            "description": "Name"
          },
          "email": {
            "type": "string",
            "description": "Email"
          },
          "phone": {
            "type": "string",
            "description": "Phone"
          },
          "message": {
            "type": "string",
            "description": "Message"
          }
        },
        "required": [
          "name",
          "email",
          "message"
        ]
      },
      "page": "/en/visibility"
    }