Skip to main content
Glama

meta_ads_lead_forms_update

Update a lead form's status to activate or archive it, controlling whether it accepts new submissions.

Instructions

Changes a lead form's lifecycle status. This tool updates only the status field — other form fields (questions, privacy_policy_url, name, follow_up_action_url, locale, advanced layout) are intentionally out of scope; Meta's post-creation mutability has shifted between versions, so mureo stays conservative. Pass status=ARCHIVED to retire a form (existing leads stay queryable; the form stops accepting new submissions). Pass status=ACTIVE to undo an archive. Mutating, reversible (re-call with the opposite value).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
account_idNoMeta Ads account ID in the format 'act_XXXXXXXXXX' (e.g. 'act_1234567890'). Optional — falls back to META_ADS_ACCOUNT_ID from the configured credentials. The leading 'act_' prefix is required.
form_idYesLead form ID to update.
statusYesTarget status. ACTIVE accepts submissions; ARCHIVED stops them. Other values (DRAFT, DELETED, DELETION_PENDING) appear in read paths but cannot be set by an operator.
Behavior4/5

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

Describes mutating yet reversible nature, and effects of each status on form behavior. No annotations present, so description carries full burden; missing details on permissions or rate limits prevent a perfect score.

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?

Five concise sentences, all essential, no redundancy. Front-loaded with main action.

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?

Lacks explicit mention of return value or error cases, but for a simple mutation tool this is acceptable. Sufficient for an informed agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

100% schema coverage, but description adds beyond schema by explaining enum values' meanings, constraints (cannot set DRAFT etc.), and fallback for account_id.

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?

Description clearly states it changes a lead form's lifecycle status and explicitly lists what it does not do (other fields out of scope), distinguishing it from any form update tool.

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?

Provides explicit when-to-use scenarios (archive/active), what not to attempt (other fields), and explains the conservative approach due to Meta's mutability shifts.

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/logly/mureo'

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