Skip to main content
Glama

aidelly

by io.github.wilzer
OverviewDiscussionsAdmin

aidelly_update_white_label_config

PATCH /white-label — update the agency's white-label branding, email settings, and visibility toggles. Domain changes and verification must go through the in-app flow. Returns the updated configuration with current domain status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bodyNoOptional body override for endpoints with sparse parameter schemas.
queryNoOptional query overrides for endpoints with sparse parameter schemas.
brand_idNo
logo_urlNoLight-mode square logo URL.
hide_earnNoHide earnings/monetization surfaces from white-label clients.
brand_nameNoAgency brand name shown to white-label clients.
favicon_urlNoFavicon URL for branded pages.
support_urlNoURL to agency support/help page.
hide_rewardsNoHide rewards and gamification surfaces.
og_image_urlNoOpen Graph image for social shares.
workspace_idNoWorkspace to operate in. Do not ask the user for this UUID — call aidelly_list_workspaces and use the `id` of the matching workspace. Optional for read operations; required when creating content.
dark_logo_urlNoDark-mode square logo URL. Falls back to logo_url if not set.
help_menu_urlNoURL for in-app help menu links.
primary_colorNoHex color for primary brand color (e.g.,
support_emailNoAgency inbox email for white-label support submissions.
watermark_urlNoWatermark image URL for reports.
email_from_nameNoFrom name for branded emails.
hide_tier_badgeNoHide tier/plan badges.
idempotency_keyYes
button_text_colorNoText/icon color on brand-colored buttons. 'auto' derives from luminance.
sidebar_logo_modeNoSidebar rendering mode — square mark+text or full logo image.
email_from_addressNoFrom email address for branded emails (must use a verified sending domain).
logo_text_font_urlNoCustom font URL for logo text in mark_text mode (must use https).
privacy_policy_urlNoPrivacy policy URL for branded emails and legal links.
saved_brand_presetNoOptional saved branding preset snapshot. Set to null to clear the preset; omit to leave alone.
watermark_settingsNoWatermark configuration object (null resets to defaults).
terms_of_service_urlNoTerms of service URL for branded emails and legal links.
hide_feature_requestsNoHide feature request UI.
logo_text_font_familyNoFont family name for logo text rendering.
logo_text_font_formatNoFont file format (woff2, woff, ttf, or otf).
sidebar_full_logo_urlNoLight-mode full sidebar logo URL (both mark and text).
show_oauth_interstitialNoWhether to show OAuth interstitial before social platform redirects.
sidebar_dark_full_logo_urlNoDark-mode full sidebar logo URL. Falls back to sidebar_full_logo_url if not set.
logo_text_font_storage_pathNoInternal storage path for the uploaded font file.
watermark_enabled_by_defaultNoWhether to include watermark on newly generated reports.
suppress_member_welcome_emailNoTri-state override for member welcome emails. null = use plan default, true/false = explicit override.
agency_staff_uses_custom_domainNoWhether agency staff access Aidelly at a custom domain.
logo_text_font_license_attested_atNoISO timestamp when font license was attested.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Description does not contradict annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true). It mentions the return value 'Returns the updated configuration with current domain status', adding value beyond annotations. However, it does not elaborate on potential side effects implied by openWorldHint.

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?

Two sentences cover purpose, constraint, and return value without fluff. Extremely concise and front-loaded.

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

Completeness3/5

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

Given the tool has 38 parameters and no output schema, the description is brief. It covers key constraints and return, but lacks explanation of side effects, timing, or relation to other tools. Adequate but not comprehensive for the complexity.

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 95%, so the schema already documents parameters well. The description adds high-level context (branding, email settings, visibility toggles) but no specific parameter details beyond what the schema provides. Baseline 3 is appropriate.

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?

Description clearly states 'update the agency's white-label branding, email settings, and visibility toggles' and identifies it as a PATCH operation. It distinctly differentiates from the sibling read tool (aidelly_get_white_label_config) and other update tools.

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

Usage Guidelines3/5

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

Provides one key exclusion: 'Domain changes and verification must go through the in-app flow', which helps avoid misuse. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites or typical use cases.

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

All aidelly toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources