Skip to main content
Glama

Fabrement

Create Contact Form 7 form

fabrement-create-cf7-form

Create a Contact Form 7 form (CF7 must be active). YOU WRITE THE MARKUP: template is the CF7 form body — your HTML plus CF7 [tags] — so the layout is whatever the design asks for, not a column of generated paragraphs. The mail body, Reply-To and attachments are derived from the tags in it. Returns { form: { id, title, shortcode, fields } } — the id is the default of the form attribute of a block (FormField). LIST-FORMS FIRST: a duplicate title is NOT refused, so calling this twice leaves two forms with the same name and no way to tell which one a page renders. Reuse the existing form, or update it with update-cf7-form. Rules: get-skill-doc {id:"forms-contract"} — read it before the first call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYesForm title (admin label).
subjectNoNotification email subject line.
messagesNoCF7 "Messages" tab as {key: text} — mail_sent_ok, validation_error, invalid_required, invalid_email, … (get-cf7-form lists every key with its current text and default). Only the keys sent change; "" resets one to the default; unknown keys are refused.
templateYesCF7 form markup — the layout is yours to write, tags included. One control per CF7 tag: [text* your-name], [email* your-email], [tel your-phone], [textarea your-message], [select your-topic "Sales" "Support"], [acceptance your-consent], [file your-cv filetypes:pdf|doc], and [submit "Send"] for the button — a trailing * means required. Everything around them is your HTML: rows, fieldsets, hints, a consent line with a link. Wrap each control in its own element and give it classes, because the CSS is written against YOUR wrappers (CF7 adds its own classes to the control itself at render time). WHAT IS DERIVED FROM THIS MARKUP: the notification mail body (one line per control), the Reply-To (the first REQUIRED email tag — an optional one is skipped, CF7 rejects a possibly-blank mailbox), and the file attachments (every file tag). A control named after a WordPress query var (name, search, author, page, day, order, term, …) is REFUSED, not renamed: prefix it the way CF7 does, your-name. At most 40 controls.
recipientNoEmail address the submissions are sent to (default: site admin).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
formYes
noteNoPresent when another form already carries this title.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

No annotations exist, so the description carries the full burden and does so: it discloses the return shape, that duplicates are silently accepted, what is derived from the markup (mail body, Reply-To from the first required email tag, attachments), what is refused (query-var control names, unknown message keys), and a hard 40-control limit. These are non-obvious behaviors an agent cannot infer from the schema.

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

Conciseness3/5

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

Dense and mostly purposeful, but the highest-stakes warning (duplicate titles are not refused) is buried after a lengthy markup lecture, and the markup/derivation explanation substantially repeats what the schema's `template` property already says. Front-loading the duplicate warning would let the reader act on it before skimming.

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?

Strong coverage for a mutation tool with no annotations and an output schema: prereqs, side effects, refusals, limits, and the follow-up call are all present. It stops short of stating permission/capability requirements or what failure looks like when CF7 is inactive, which an agent may still need.

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; the description earns a 4 by adding semantics the schema doesn't give — the returned form id is the default of a block's `form` attribute, and the markup drives derived mail/Reply-To/attachment behavior. It loses a point because much of the `template` guidance mirrors the schema's own long template description rather than adding to it.

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?

States a specific verb and resource ('Create a Contact Form 7 form') plus the enabling precondition ('CF7 must be active'), and immediately distinguishes itself from update-cf7-form. An agent knows exactly what this does and which sibling handles the other case.

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?

Explicit when-to-use and when-not-to: 'LIST-FORMS FIRST' with the concrete consequence spelled out (duplicate titles are not refused, leaving two identical forms), and it names both alternatives — reuse the existing one or call update-cf7-form. It also gates first use on get-skill-doc {id:"forms-contract"}.

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.

Resources