Skip to main content
Glama

Honeyfield Marketing MCP

Meta Ads: Archive lead form

meta_archive_lead_form
Destructive

Lead-Formular archivieren — die einzige Änderung, die Meta an einem veröffentlichten Instant Form erlaubt (Korrektur = archivieren + neu anlegen). Anzeigen, die das Formular nutzen, vorher pausieren oder umstellen. Löschen ist bei Meta nicht möglich. Rückgabe zurückgelesen: {success, form_id, name, status: 'ARCHIVED'}; sonst error=archive_not_confirmed. Das Formular muss zur gewählten Page des Werbekontos gehören, sonst error=foreign_object (nichts geändert). form_id: aus meta_list_lead_forms. page_id: wie bei meta_list_lead_forms. workspace: Slug des Kunden-Workspace (optional bei nur einem Workspace).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "form_id": "<form_id>"
    },
    "name": "meta_archive_lead_form"
  }
}

Input Schema

NameRequiredDescriptionDefault
form_idYes
page_idNo
workspaceNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the destructiveHint=true annotation, the description explains the destructive-adjacent behavior in detail: archiving is irreversible in the sense that deletion is impossible, ads using the form should be paused or switched first, and a foreign-object guard prevents unintended changes. It also documents the return shape and the archive_not_confirmed error path.

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?

The description is front-loaded with the core operation and its main constraint, then moves through prerequisites, error behavior, and parameter sourcing without filler. Every line contributes operational information needed to call the tool safely.

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 destructive mutation with a simple three-parameter schema, the description covers the operation, prerequisites, side effects, error handling, return confirmation, and parameter origins. Although an output schema exists, the explicit return summary is helpful rather than redundant, and no critical calling information is missing.

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 0%, so the description carries the burden. It usefully explains that form_id comes from meta_list_lead_forms, that workspace is an optional customer-workspace slug when only one exists, and references page_id as behaving like meta_list_lead_forms. The page_id explanation is less precise than ideal, but all three parameters receive meaningful context.

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 states a specific verb and resource ('Lead-Formular archivieren') and immediately clarifies the unique Meta constraint: archiving is the only permitted change to a published Instant Form, with correction requiring archive + recreate. This distinguishes it clearly from sibling tools such as meta_create_lead_form and meta_list_lead_forms.

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 gives explicit operational guidance: pause or repoint ads using the form beforehand, notes that deletion is impossible, and states the prerequisite that the form must belong to the selected ad account page or else foreign_object is returned. It also points to meta_list_lead_forms for obtaining form_id and explains workspace optionality.

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