Skip to main content
Glama

update_project_settings

Update project settings while retaining unspecified fields; pass null to clear optional values. Configure outbound channels, follow-up cadence, sender identity, and compliance options.

Instructions

Update user-editable project settings. Any omitted field keeps its current value. Pass null to clear nullable fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
projectIdYesProject name or ID
outboundModeNo"send" sends immediately; "draft" stores as reviewable LeadAce drafts instead of sending.
inquiryCtaUrlNoCTA URL, https:// only. For inquiryCtaType="meeting": optional scheduling URL — when null the meeting button is notify-only. For inquiryCtaType="signup": the signup page URL, required.
inquiryPdfUrlNoPublic URL for the "download PDF" button on the landing page. https:// only.
footerOverrideNoCustom footer replacing the default compliance footer VERBATIM on every outbound message (email, and form / SNS draft text) — when set, it must itself carry the "---" separator and the legally required disclosures. null restores the default. Mutually exclusive with inquiryLandingEnabled (400).
inquiryCtaTypeNoLanding CTA mode. "meeting" (default): Book/Request meeting button, inquiryCtaUrl optional (scheduling URL). "signup": Sign up button redirecting to inquiryCtaUrl, which is required in this mode.
senderJobTitleNoJob title / role shown alongside senderDisplayName on the inquiry-landing header. No-op when senderDisplayName is null.
targetLanguageNoLanguage of this project's outbound messages (default "en"): sets the compliance-footer / identity localization and the language outbound subjects and bodies are written in. Independent of targetCountries; recipient-facing web pages (inquiry landing, unsubscribe) follow the visitor's browser language instead.
inquiryOneLinerNoSingle-sentence value prop shown above the chat input on the landing page.
inquiryVideoUrlNoYouTube/Vimeo unlisted video URL embedded on the landing page. https:// only.
targetCountriesNoCountry codes that further narrow the compliance-level send allowlist. Empty array (default) = no project-level restriction; non-empty = explicit allowlist.
followUpSequenceNoFollow-up sequence for unanswered prospects. gapDays = relative waits in DAYS before each next touch (default [3,7,7]). Whole-object replace: omitting `enabled` sets it false, disabling follow-ups AND clearing in-progress sequences — pass enabled:true explicitly to keep them on while changing cadence.
inquiryChatBriefNoBriefing for the inquiry-landing chat agent. null disables chat input but keeps the rest of the landing page rendering.
outboundChannelsNoChannels the project is allowed to use for outbound. Default: email, form, sns_twitter, sns_linkedin — "platform" must be enabled explicitly. Empty array pauses automated outbound (manual per-draft send still works).
senderEmailAliasNoGmail Send-As alias to use as From: address. null = primary Gmail. Ignored when the project sends from a custom SMTP mailbox.
inquiryBrandColorNoLanding-page accent color.
senderCompanyNameNoCompany / brand name shown to recipients on the inquiry landing. Distinct from the compliance-footer legal name and the internal workspace name. null omits it.
senderDisplayNameNoPersonal name shown as the email From: display name and on the inquiry-landing header.
unsubscribeEnabledNoAttach the RFC 8058 List-Unsubscribe one-click headers to outbound email.
inquiryBrandLogoUrlNoPublic URL for the brand logo shown on the landing page. https:// only.
maxReapproachCyclesNoHard cap on rejection cycles before forcing rejected + DNC. Default 3.
inquiryDarkBackgroundNoLanding background mode: false = light (default), true = dark.
inquiryLandingEnabledNoWhen true, outbound emails include an inquiry-landing URL footer that hosts a per-recipient AI chat, meeting-request button, and unsubscribe-with-reason flow.
noResponseRecycleDaysNoDays after a sent outreach before the prospect is re-eligible if no response arrived. Default 90. Only advances the re-eligibility window forward, never shortens a longer existing deferral (e.g. a rejection-feedback 12-month window).
unspecifiedRecontactWindowMonthsNoMonths to defer when rejection feedback preferred_recontact_window is "unspecified". Default 3.
Behavior3/5

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

With no annotations, the description carries the full burden. It discloses key partial-update semantics ('Any omitted field keeps its current value') and null-clearing behavior, which is valuable. However, it does not mention return values, error conditions, or side effects beyond what the schema already describes.

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, front-loaded with the main purpose, and zero unnecessary words. The description is concise and well-structured.

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 high complexity (25 params, nested objects, no output schema, no annotations), the description is minimal. It covers core update semantics but omits return-value behavior and any high-level caution about interactions (though schema descriptions cover many). Leveraging the rich schema, it is adequate but not fully complete.

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 baseline is 3. The description adds a universal patch semantic (omitted equals keep, null clears) that applies to all 25 parameters, which is not repeated in each schema property. This adds value beyond the structured schema.

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 clearly states the action ('Update') and the resource ('user-editable project settings'). It distinguishes from siblings like get_project_settings (read) and update_organization/update_tenant_settings (different scopes) by specifying project-level settings.

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?

The scope is implied by 'project settings', but there is no explicit guidance on when to use this tool versus update_organization or update_tenant_settings. Given the sibling list includes several update tools, explicit alternative naming would improve clarity.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aitit-inc/leadace'

If you have feedback or need assistance with the MCP directory API, please join our Discord server