Skip to main content
Glama

Route Meta leads to a pipeline

set_meta_lead_route

Choose which pipeline new Meta lead-ad leads go to. Give page_id alone to set the Page's route (every form on that Page), or page_id and form_id to override one form. pipeline_id null clears the route at that level (a Page falls back to the account default; a form falls back to its Page). Only connected Pages, and only forms that have already sent a lead, can be routed: get both from list_meta_lead_routes. Clearing (pipeline_id null, no form_id) also works for a Page that is no longer connected (stale_pages) and clears that Page's form routes too, since leftover routes would otherwise block deleting the pipeline they name. Existing deals do not move; it applies to leads that arrive from now on.

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": {
      "page_id": "<page_id>",
      "pipeline_id": "<pipeline_id>"
    },
    "name": "set_meta_lead_route"
  }
}

Input Schema

NameRequiredDescriptionDefault
form_idNoA form id from list_meta_lead_routes, to override just that form
page_idYesA connected Page id from list_meta_lead_routes
pipeline_idYesTarget pipeline id from list_pipeline_stages, or null to clear

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnlyHint=false, destructiveHint=false); the description adds the real behavioral weight: routing preconditions (only connected Pages, only forms that have sent a lead), the fallback chain when a route is cleared, the cascade side effect (clearing a Page also clears its form routes, to unblock pipeline deletion), and that existing deals do not move. That is exactly the beyond-annotations context an agent needs.

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?

Front-loaded with the core purpose, then progressively discloses the scoping modes, clearing semantics, and preconditions. Dense and mostly earns its words, but the trailing stale-Pages/pipeline-deletion rationale is a long subordinate clause that could be trimmed without losing actionable information.

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 3-parameter configuration tool with no output schema, it covers everything an agent needs: preconditions, the two write modes, clearing behavior, cascade effects, and non-effects on existing deals. No return-value documentation is required since no output schema exists.

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, but the description genuinely adds meaning: page_id alone vs. page_id+form_id changes the scope of the write, and pipeline_id=null is a clearing operation with defined fallback semantics. It does not add format/syntax details beyond the schema, which is fine at this coverage level.

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+resource: 'Choose which pipeline new Meta lead-ad leads go to.' It names the sibling tool to consult first (list_meta_lead_routes), so the agent can separate this configuration tool from the listing tool without opening either 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?

Explicitly distinguishes the two invocation modes (page_id alone = whole Page; page_id+form_id = single-form override), states when to use the null pipeline_id to clear, and names the prerequisite lookup tool. It even carves out the special case for stale Pages that can only be cleared, not set.

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