Skip to main content
Glama

Inclusify Accessibility

by com.inclusifyapp

Change how the accessibility widget looks and which profiles it offers

set_widget_appearance
DestructiveIdempotent

Use this when the user wants the Inclusify widget on their site to look different — match brand colour, move it off something it covers, change its size or icon — or to change which accessibility PROFILES it offers visitors. WRITES to this website's Inclusify configuration, never to the site's code or theme: it changes what the widget bundle renders. Takes effect within about a minute; the edge cache is purged as part of the change. Every setting is optional and anything you leave out is left exactly as it is, so you can change one without knowing the others. This REQUIRES CONFIRMATION — call without "confirm" first, show the user the preview, then call again with the token once they agree — because the result is visible to that site's real visitors. Removing an accessibility profile is the consequential part: it takes an accommodation away from visitors who may be relying on it, so the preview names each one. Note that "enabledProfiles" is a COMPLETE REPLACEMENT LIST, not an addition — whatever you pass becomes the whole set, so include the ones already on that should stay on. The account owner is emailed a record with a link to undo it. Needs the STARTER plan or above, matching the panel. Shopify-billed stores cannot use this at all — they customise the widget from the Shopify app. To turn the widget off entirely, use set_widget_enabled instead. One setting here needs more than Starter: "hideBranding", which removes the Inclusify wordmark from the widget's footer, needs the ENTERPRISE plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
confirmNoLeave this out on the first call to get a preview of exactly what would change, plus a confirmation token. Call again with the same arguments and that token to apply the change. The token lasts 10 minutes and works once.
websiteYesThe website domain as registered in Inclusify, e.g. "example.com".
languageNoWidget interface language. Anything other than English needs a plan with more than one language.
positionNoWhich corner the widget button sits in.
triggerIconNoWhich icon the button shows.
triggerSizeNoButton size in pixels, 40 to 80.
hideBrandingNoWhether to remove the Inclusify wordmark from the bottom of the widget panel. ENTERPRISE ONLY; on any other plan this is refused rather than quietly ignored. It removes our wordmark and its link and nothing else: the widget cannot be rebranded with the customer's own logo or name, the floating button keeps its accessibility glyph (that is a standard icon visitors look for, not branding, and its colour and size are separate settings here), and the link to the customer's own accessibility statement is unaffected.
primaryColorNoSix-digit hex, e.g. "#0066ff". The widget button and accents use it.
showOnMobileNoWhether the widget appears on small screens.
enabledProfilesNoThe accessibility profiles offered to visitors, as a complete replacement list — whatever you pass becomes the whole set, so include the ones already on that should stay on. Removing one takes that accommodation away from visitors using it.
triggerElementIdNoThe id of an element on the CUSTOMER'S OWN site that opens the widget — usually a footer or menu link they have styled themselves, e.g. "footer-accessibility". On every page where that element exists the floating button is not rendered, so their link becomes the only visible way in; on pages where it is missing the floating button comes back, so the widget is never unreachable. An element id, NOT a CSS selector, and without the leading "#". Pass null to remove it and go back to the floating button. Setting this does not put the element on their site — they add the id to their own theme; if you have not confirmed the element exists, say so rather than assuming.
hideForeverEnabledNoWhether visitors get a "don't show again" option. Needs the plan that includes it.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / properties / hideBranding
      Added value: +{
+  "description": "Whether to remove the Inclusify wordmark from the bottom of the widget panel. ENTERPRISE ONLY; on any other plan this is refused rather than quietly ignored. It removes our wordmark and its link and nothing else: the widget cannot be rebranded with the customer's own logo or name, the floating button keeps its accessibility glyph (that is a standard icon visitors look for, not branding, and its colour and size are separate settings here), and the link to the customer's own accessibility statement is unaffected.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / language / enum
      Previous value: -[
-  "en",
-  "es",
-  "fr",
-  "de",
-  "it",
-  "pt",
-  "nl",
-  "ja",
-  "zh"
-]New value: +[
+  "en",
+  "af",
+  "am",
+  "ar",
+  "hy",
+  "az",
+  "eu",
+  "bn",
+  "bg",
+  "my",
+  "ca",
+  "zh",
+  "zh-TW",
+  "hr",
+  "cs",
+  "da",
+  "nl",
+  "en-GB",
+  "et",
+  "tl",
+  "fi",
+  "fr",
+  "fr-CA",
+  "ka",
+  "de",
+  "el",
+  "gu",
+  "he",
+  "hi",
+  "hu",
+  "id",
+  "ga",
+  "it",
+  "ja",
+  "kn",
+  "km",
+  "ko",
+  "ku",
+  "lo",
+  "lv",
+  "lt",
+  "ms",
+  "ml",
+  "mr",
+  "ne",
+  "no",
+  "fa",
+  "pl",
+  "pt",
+  "pt-BR",
+  "pa",
+  "ro",
+  "ru",
+  "sr",
+  "si",
+  "sk",
+  "sl",
+  "es",
+  "es-MX",
+  "sw",
+  "sv",
+  "ta",
+  "te",
+  "th",
+  "tr",
+  "uk",
+  "ur",
+  "vi",
+  "cy",
+  "xh",
+  "zu"
+]
  3. Changed1 schema field changed
    • addedInput schema / properties / triggerElementId
      Added value: +{
+  "description": "The id of an element on the CUSTOMER'S OWN site that opens the widget — usually a footer or menu link they have styled themselves, e.g. \"footer-accessibility\". On every page where that element exists the floating button is not rendered, so their link becomes the only visible way in; on pages where it is missing the floating button comes back, so the widget is never unreachable. An element id, NOT a CSS selector, and without the leading \"#\". Pass null to remove it and go back to the floating button. Setting this does not put the element on their site — they add the id to their own theme; if you have not confirmed the element exists, say so rather than assuming.",
+  "type": [
+    "string",
+    "null"
+  ]
+}
  4. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses critical behaviors: it writes to configuration not site code/theme, works via edge-cache purge within a minute, requires confirmation, emails the owner with an undo link, and warns that removing profiles is consequential. It also explains the complete-replacement semantics of enabledProfiles and the Enterprise-only hideBranding restriction. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long but densely informative, and the primary use case is front-loaded. It could be tightened, but nearly every sentence adds a necessary constraint or behavioral note, so it earns a solid score rather than being penalized for its length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 12 parameters, no output schema, and a destructive mutation, the description covers all essential invocation context: plans, Shopify exclusion, confirmation workflow, replacement-list semantics, undo email, and the distinction from set_widget_enabled. An agent has enough information to call it correctly and safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it frames enabledProfiles as consequential because removing a profile affects relying visitors, states that the preview names each removed profile, and clarifies that omitted settings are left unchanged. This enriches parameter understanding without replacing the schema's own detailed 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 states a specific verb and resource: 'Use this when the user wants the Inclusify widget on their site to look different' and 'or to change which accessibility PROFILES it offers visitors.' It clearly distinguishes this from set_widget_enabled and other sibling tools by covering appearance and profile changes specifically.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives explicit when-to-use guidance, plan requirements, Shopify-billed store exclusion, and names the alternative tool: 'To turn the widget off entirely, use set_widget_enabled instead.' It also details the confirmation flow, so an agent knows the correct call sequence.

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

All Inclusify Accessibility toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation4/5

The descriptions do exceptional cross-referencing work, explicitly separating near-neighbor pairs (add_website vs add_domain, list_alt_findings vs check_page_alt_text, plan_options vs billing_link, widget_status vs widget_usage). A few clusters remain that an agent could confuse without reading carefully, notably site_overview vs compliance_status (both report statement existence and scan-record state) and crawl_summary vs list_monitored_pages vs site_overview (all touch coverage numbers). Overall, distinct purposes are clearly delineated despite the large surface.

Naming Consistency4/5

All names are lowercase snake_case with strong family patterns: list_* (5 tools), add_* (3), set_* (7), plus org_* and *_history pairs. The main inconsistency is the mix of verb-led names (list_violations, set_slack_channel, start_crawl) with noun-led read names (site_overview, compliance_status, widget_usage, next_steps), but the noun-led names follow a coherent 'what it returns' vocabulary (status, summary, history, overview, rollup). Minor deviations rather than chaos.

Tool Count3/5

36 tools is heavy and sits above the 25-tool threshold where agent navigation starts to degrade, but the server covers a genuinely broad domain: website lifecycle, monitoring, four finding types, four live-audit tools, seven config setters, org rollups, billing, and CI. Most tools earn their place and none are duplicates, but several could plausibly be merged (set_slack_channel/set_slack_events/set_monitoring_settings into one notifications tool; list_violations/list_alt_findings/list_content_findings with a filter). The count is on the edge of unwieldy for an agent's tool-selection step.

Completeness3/5

The read/audit/analysis side is rich and well-covered: findings, history, live checks, org rollups, coverage, and validation all have tools. However, the write side is one-directional: add_monitored_pages is explicitly add-only, and there is no remove_website, remove_domain, or remove_monitored_pages, so teardown and 'stop monitoring this page' requests hit dead ends that the descriptions acknowledge belong to the panel. Statement content writing and widget installation are also panel/browser-only by design, which is documented but still leaves those operations outside the agent's reach.

Resources