Skip to main content
Glama

dialogbrain

by io.github.saloprj
OverviewDiscussionsAdmin

webhooks_configure_enrichment

Enable enrichment on an agent's webhook trigger so reference-only webhook payloads are resolved to full data before the agent runs. One tool for every provider — choose provider and pass its config.

Providers & required config:

  • meta_leadgen (Meta/Facebook Lead Ads): config = {app_id, app_secret, user_access_token}. The user token needs pages_show_list + leads_retrieval (+ pages_manage_metadata; add business_management to auto-discover Business-Manager pages that /me/accounts omits). Stores all page tokens encrypted per workspace and resolves each lead's name/email/phone. Reuses the existing webhook URL (no token rotation); creates a webhook trigger if the agent has none.

  • tiktok_leadgen (TikTok Instant Form and direct-message leads): config = {access_token, advertiser_ids?}. access_token is a TikTok Marketing API advertiser token issued to DialogBrain's Business app; without advertiser_ids every ad account the token reaches is subscribed. Adds a separate webhook trigger on the agent (a Meta-wired trigger is left alone) and subscribes it to LEAD events; each lead arrives with its answers, signature-verified.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
configYesProvider-specific configuration/credentials. For meta_leadgen: {app_id, app_secret, user_access_token}. For tiktok_leadgen: {access_token, advertiser_ids?}.
agent_idYesID of the agent whose webhook trigger should be enriched.
providerYesEnrichment provider to configure.
in_workspaceNoRun this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / in_workspace
      Added value: +{
+  "description": "Run this one call in this workspace id instead of the session's. Nothing is stored; other sessions are not affected.",
+  "type": "integer"
+}
  2. Added
  3. Removed
  4. Added

TDQS

A4.5/5.0
Behavior5/5

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

Adds substantial behavioral detail beyond the annotations: page tokens stored encrypted per workspace, no token rotation, trigger creation when absent, a separate trigger for TikTok that leaves a Meta-wired trigger alone, LEAD-event subscriptions, and signature verification. This is exactly the side-effect and credential context the flat annotation hints cannot convey.

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-loads the core purpose, then uses a per-provider bullet structure that keeps the dense scope/behavior details scannable. It is long, but nearly every clause carries actionable information rather than 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?

For a mutation tool with no output schema, the description covers config requirements, credential handling, and side effects thoroughly. It omits what the call returns and how to later disable enrichment, which are minor gaps against an otherwise complete picture.

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, but the description goes further — it spells out which scopes the Meta user_access_token requires (pages_show_list, leads_retrieval, business_management) and that omitting advertiser_ids subscribes every reachable ad account. It adds real meaning over the generic per-field schema text.

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 and resource — 'Enable enrichment on an agent's webhook trigger' — and clarifies scope with 'One tool for every provider,' which distinguishes it from the provider-specific or trigger-management siblings. An agent knows exactly what this does without opening 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for when this applies (reference-only payloads needing resolution before the agent runs) and how behavior differs by situation (reuses existing URL, creates a trigger if none exists, adds a separate trigger for TikTok). It does not explicitly name alternatives such as agents_trigger_create/update, so the 'vs sibling' routing is implied rather than stated.

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

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