Skip to main content
Glama

Adsap

by ai.adsap
OverviewDiscussionsAdmin

Manage Instant Form (create / duplicate / archive / reactivate)

adsap_manage_instant_form

Create, duplicate, archive or reactivate a Meta Instant Form: the lead form people fill in without leaving Facebook or Instagram. Use it when the user wants a lead ad and has no suitable form yet, or wants a changed version of an existing form. IMPORTANT: Meta never lets a form be edited or deleted once created, only archived, so dry_run defaults TRUE: call once to preview (free, creates nothing), show the user the summary, then call again with dry_run:false after they confirm. To 'edit' a form, duplicate it with the changed sections and archive the old one. Before create, ask the user for the questions. The privacy policy link (Meta requires one) and the thank-you screen (headline, optional text, button or no button) can be saved once per Facebook Page by the user in Adsap, on the Instant Forms page: leave privacy_policy and thank_you out, and the preview applies the saved defaults and lists them (defaults_used, defaults_applied): show them to the user. If the preview says they are missing, ask the user for them. Never invent a privacy link or a thank-you text, and suggest wording only if the user asks you to. Not available: conditional logic (Meta keeps it for its own interface), and, not built in Adsap yet, appointment, store locator and national ID questions and file downloads on the thank-you screen. The returned form_id goes into creative_spec.leadgen_form_id of adsap_create_ad, on an ad set whose conversion location is Instant Forms (or Website and Instant Forms) and that promotes the SAME Page. List a Page's forms with adsap_list_meta_assets (asset_type instant_forms).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formNocreate: name and questions are required; privacy_policy and thank_you come from the defaults saved for the Page when you leave them out. duplicate: a NEW name plus only the sections to replace; a section you send replaces the whole section, everything else is copied as is.
actionYescreate a new form; duplicate an existing one with changes (the only way to 'edit', since Meta never lets a form be modified); archive (hide it and block it from new ads); reactivate an archived form.
dry_runNoDefault true = preview: checks everything with Meta and creates nothing. Call again with false only after the user confirms. A created form can NEVER be edited or deleted, only archived.
form_idNoRequired for duplicate, archive and reactivate.
page_idNoRequired for every action. Numeric id of the Facebook Page that owns the form. A form belongs to ONE Page and only works in ads that run for that Page.
ad_account_idYesMeta ad account (act_...) the Page is connected to. Used for access checks.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / form / description
      Previous value: -"create: the whole form (name, questions, privacy_policy and thank_you are required). duplicate: a NEW name plus only the sections to replace; a section you send replaces the whole section, everything else is copied as is."New value: +"create: name and questions are required; privacy_policy and thank_you come from the defaults saved for the Page when you leave them out. duplicate: a NEW name plus only the sections to replace; a section you send replaces the whole section, everything else is copied as is."
    • changedInput schema / properties / form / properties / privacy_policy / description
      Previous value: -"REQUIRED by Meta on every form. Ask the user for the link; never invent one."New value: +"Meta requires one on every form. Leave it out to use the default the user saved for this Page in Adsap. If none is saved the preview says so: then ask the user for the link, and never invent one."
    • addedInput schema / properties / form / properties / questions / items / properties / key
      Added value: +{
+  "description": "Internal name the answer is delivered under. Omit it for a new question. When you resend a question that came from adsap_get_instant_form (a duplicate with changed questions), keep its key, so leads keep arriving under the same name in the user's CRM.",
+  "type": "string"
+}
    • changedInput schema / properties / form / properties / thank_you / description
      Previous value: -"REQUIRED: the screen people see after sending the form."New value: +"The screen people see after sending the form. Leave it out to use the default the user saved for this Page in Adsap. If none is saved the preview says so: then ask the user what it should say. Never write the headline or the text yourself unless they ask you to."
    • changedInput schema / properties / page_id / description
      Previous value: -"Numeric id of the Facebook Page that owns the form. A form belongs to ONE Page and only works in ads that run for that Page."New value: +"Required for every action. Numeric id of the Facebook Page that owns the form. A form belongs to ONE Page and only works in ads that run for that Page."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations present, the description carries the full behavioral burden, and it succeeds. It discloses that dry_run defaults to TRUE, that preview creates nothing, that Meta never allows a form to be edited or deleted after creation, and that saved Page defaults may be applied automatically. It also warns the agent never to invent privacy links or thank-you copy, which is important safety behavior beyond 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.

Conciseness4/5

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

The description is long but dense, with nearly every sentence carrying a workflow instruction, constraint, or safety caveat. The most important rule (dry_run defaults TRUE and forms can never be deleted) is front-loaded. It loses a point for being somewhat heavy and for restating the no-edit rule that also appears in the schema, but it remains well-structured and relevant.

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 six parameters, nested objects, four actions, and no output schema, the description is unusually complete. It covers all actions, required user inputs, Page-default behavior, unsupported features, the downstream ad-creation integration, and how to list existing forms. Nothing critical is missing for an agent to call the tool correctly.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful operational semantics beyond the schema, such as leaving privacy_policy and thank_you out to use saved Page defaults, the dry_run confirmation loop, and how the returned form_id feeds creative_spec.leadgen_form_id. It does not walk through every parameter, but the schema already documents them thoroughly.

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 opens with four concrete actions (create, duplicate, archive, reactivate) and clearly names the resource: Meta Instant Form. It distinguishes this tool from sibling tools by explaining the no-edit constraint, the duplicate-to-edit workflow, and pointing to adsap_list_meta_assets for listing forms. An agent can tell exactly what this tool does without reading the schema.

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?

It states explicitly when to use the tool: when the user wants a lead ad and has no suitable form yet, or wants a changed version of an existing form. It provides the dry_run preview-then-confirm workflow, tells the agent to ask the user for questions/privacy/thank-you content, names unsupported features, and routes related operations to sibling tools like adsap_list_meta_assets and adsap_create_ad.

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

All Adsap 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