Meta Cloud API MCP Server

update_flow_metadata

Update an existing WhatsApp Flow's metadata, including its name, categories, and endpoint URI.

Instructions

Update metadata of an existing WhatsApp Flow (name, categories, endpoint URI)

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": {
      "flow_id": "<flow_id>"
    },
    "name": "update_flow_metadata"
  }
}

Input Schema

Name	Required	Description
`name`	No	New flow name
`flow_id`	Yes	The Flow ID to update
`categories`	No	Updated flow categories
`endpoint_uri`	No	Updated endpoint URI

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description bears the full burden of disclosing behavioral traits. It fails to mention whether updates overwrite existing metadata, required permissions, potential side effects, or how errors are handled. The description is purely functional with no transparency beyond the action itself.

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 a single, focused sentence that front-loads the verb and resource, then lists the relevant fields in parentheses. Every word contributes, and there is no redundancy or filler.

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?

Given the tool's simplicity and the fact that the schema fully documents all parameters, this description is reasonably complete for a basic metadata update operation. It could be improved by noting that no output schema exists and adding a note about idempotency or partial updates, but the essentials are covered.

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

Parameters3/5

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

The input schema already describes all four parameters, achieving 100% coverage. The description only restates the field names without adding any additional meaning, such as format constraints or relationships between parameters, so it adds no value beyond the schema.

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 clearly states the tool updates metadata of an existing WhatsApp Flow and specifies the exact fields (name, categories, endpoint URI). This distinguishes it from sibling tools like update_flow_json, which likely handle the flow's JSON definition, making the purpose unambiguous.

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?

The description implies usage for updating an existing flow's metadata rather than its JSON structure, but it does not explicitly state when to prefer this tool over update_flow_json or other alternatives. It also lacks mention of prerequisites like the flow existing.

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