Skip to main content
Glama

Update project

update_project
Idempotent

Use to patch website settings. Nested email sets notification templates: email.subject, email.from_name, email.intro, email.footer_mode (furrow | minimal | off), email.include_meta. Optional branding updates the team (mode furrow | off | agency on yearly only; other modes return plan_limit on free). Set uploads_enabled and upload_allowed_types here — forms inherit them. notify_cc and notify_bcc copy every notification email (Bcc stays hidden from the client — use it for an agency's quiet copy); forms inherit them. notify_phones (E.164) get a short new-lead text per clean submission once the team has Twilio set up (update_account sms); forms inherit them. Email templates support {{project.name}}, {{project.slug}}, {{form.name}}, {{form.slug}}, {{count}} (1-based clean submissions on this form, including the current one), and any submission field such as {{name}} or {{email}}. Use a fallback with {{name | "New submission"}}. Missing fields render empty and never error. Do not pass HTML; Furrow renders one owned layout. Plans are capacity, not a feature ladder. Free: one workspace, 100 clean submissions/month pooled on the team, 3 active (non-archived) projects, 30-day submission retention, and email.footer_mode / branding.mode stay furrow (other values return plan_limit). Yearly ($199/year): extra workspaces, 10,000 submissions/month, unlimited projects, 730-day retention, branding.mode furrow | off | agency. Expansion packs are $99/year each and add 5,000 submissions/month on a yearly account. MCP, webhooks, snippets, inheritance, Turnstile, and email templates stay available on free. Spam, honeypot, and rejected posts do not count. Use create_upgrade_link to hand a human a Stripe Checkout (or Customer Portal) URL. Pass product=expansion on a yearly team to add a pack. File inputs use multipart POST (name="resume[]" for multiple). Enable uploads on the project first. Downloads are the project inbox at files_url, with the form slug as a folder — never put that URL in a public snippet. Null Turnstile or webhook fields clear them. Do not use this to create forms. Updating project keys changes resolved settings on existing forms unless a form override is set.

Input Schema

NameRequiredDescriptionDefault
nameNoNew project display name.
emailNoNotification email template for the project: subject, from_name, intro, footer_mode, include_meta.
brandingNoPer-project branding override for notification emails and hosted pages.
from_nameNoLegacy From display name. Prefer email.from_name.
notify_ccNoCc'd on every notification email (max 10). Copies only: an email still needs at least one notify_emails address, and an address on more than one list is sent once (To, then Cc, then Bcc). Copies get [Potential spam] emails too.
notify_bccNoBcc'd on every notification email (max 10), hidden from the other recipients — use it when an agency wants a silent copy of a client's leads. Copies only: an email still needs at least one notify_emails address, and an address on more than one list is sent once (To, then Cc, then Bcc). Copies get [Potential spam] emails too.
project_idYesProject (website) id from list_projects, create_project, or bootstrap_site.
webhook_urlNoPublic https endpoint that receives a signed JSON POST per clean submission. Null disables it.
notify_emailsNoReplace the notification recipients (max 10). Cannot be emptied while the project has no webhook_url.
notify_phonesNoReplace the text-alert numbers (E.164, max 5). Empty array turns texts off. Text messages need the team's own Twilio account first (update_account sms).
honeypot_fieldNoName of the hidden honeypot input the snippet emits. Defaults to _gotcha.
webhook_secretNoHMAC-SHA256 secret for the X-Furrow-Signature header. Omit to have one generated and returned.
allowed_domainsNoReplace the allowed hostnames. Empty array accepts any origin.
uploads_enabledNoAccept multipart file fields on this project's forms.
turnstile_secretNoCloudflare Turnstile secret used to verify tokens server-side. Null removes it.
upload_max_filesNoMax files per submission (up to 20).
rate_limit_per_ipNoMax submissions per IP within rate_limit_window_s.
require_turnstileNoReject submissions that lack a valid Turnstile token.
turnstile_site_keyNoCloudflare Turnstile site key for the frontend widget. Null removes it.
rate_limit_window_sNoRate-limit window in seconds (max 86400).
default_redirect_urlNoWhere classic HTML posts redirect after success. Null returns JSON/inline success instead.
upload_allowed_typesNoAllowed upload MIME types, e.g. application/pdf or image/*.
upload_max_file_bytesNoMax bytes per file (up to 25 MB).
upload_max_total_bytesNoMax total upload bytes per submission (up to 50 MB).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / notify_bcc / items / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
    • changedInput schema / properties / notify_cc / items / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
    • changedInput schema / properties / notify_emails / items / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. Changed2 schema fields changed
    • addedInput schema / properties / notify_bcc
      Added value: +{
      +  "description": "Bcc'd on every notification email (max 10), hidden from the other recipients — use it when an agency wants a silent copy of a client's leads. Copies only: an email still needs at least one notify_emails address, and an address on more than one list is sent once (To, then Cc, then Bcc). Copies get [Potential spam] emails too.",
      +  "items": {
      +    "format": "email",
      +    "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      +    "type": "string"
      +  },
      +  "maxItems": 10,
      +  "type": "array"
      +}
    • addedInput schema / properties / notify_cc
      Added value: +{
      +  "description": "Cc'd on every notification email (max 10). Copies only: an email still needs at least one notify_emails address, and an address on more than one list is sent once (To, then Cc, then Bcc). Copies get [Potential spam] emails too.",
      +  "items": {
      +    "format": "email",
      +    "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
      +    "type": "string"
      +  },
      +  "maxItems": 10,
      +  "type": "array"
      +}
  3. Changed2 schema fields changed
    • changedInput schema / properties / notify_emails / description
      Previous value: -"Replace the notification recipients (max 10)."New value: +"Replace the notification recipients (max 10). Cannot be emptied while the project has no webhook_url."
    • addedInput schema / properties / notify_phones
      Added value: +{
      +  "description": "Replace the text-alert numbers (E.164, max 5). Empty array turns texts off. Text messages need the team's own Twilio account first (update_account sms).",
      +  "items": {
      +    "maxLength": 32,
      +    "type": "string"
      +  },
      +  "maxItems": 5,
      +  "type": "array"
      +}
  4. First observed

TDQS

A3.8/5.0
Behavior5/5

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

The description adds substantial behavior beyond the annotations: plan limits that return plan_limit, token rendering and fallback behavior, inheritance by forms, null-clearing semantics for Turnstile and webhook fields, and the side effect that updating project keys changes resolved settings on existing forms. These details materially help an agent predict the tool's effects.

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

Conciseness2/5

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

The description is very long and mixes update_project behavior with pricing details, create_upgrade_link usage, multipart submission instructions, download inbox warnings, and other tangential context. The purpose is front-loaded, but many sentences do not directly help an agent invoke this specific update tool.

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

Completeness4/5

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

For a 24-parameter nested update tool with annotations but no output schema, the description covers the most important behavior: plan constraints, inheritance, token rendering, null clearing, upload prerequisites, and the prohibition on using it to create forms. It is not perfectly focused, but it is complete enough for correct invocation.

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 schema already carries most parameter semantics. The description still adds useful meaning beyond it, especially token syntax and fallbacks for email templates, inheritance rules for uploads and notification fields, and null-clearing behavior for some fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with 'Use to patch website settings,' giving a clear verb and resource, and it enumerates many project-level fields. It also says 'Do not use this to create forms,' which distinguishes it from creation siblings, though it does not explicitly contrast update_form or update_team.

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?

It gives some usage context, such as setting uploads and notification settings here because forms inherit them, and it explicitly warns against using the tool to create forms. However, it does not clearly say when to choose update_project over update_form or update_team, and the create_upgrade_link guidance is about a sibling tool rather than this one.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.