Skip to main content
Glama

create_webhook

Create a new webhook by providing a name, URL, and trigger events to automate real-time data sync with Mautic.

Instructions

Create new webhook

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesWebhook name
descriptionNoWebhook description
webhookUrlYesWebhook URL
secretNoWebhook secret
eventsOrderbyDirNoEvent order direction
triggersYesEvent types to trigger webhook
Behavior1/5

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

No annotations provided, and description fails to disclose any behavioral traits like idempotency, side effects, or authentication needs. Critical gap for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence is concise but lacks structure. It is front-loaded but too minimal to provide sufficient guidance for an agent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With 6 parameters, no output schema, and no annotations, the description is incomplete. Lacks info on return value, validation, or error handling.

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?

Schema description coverage is 100%, so baseline is 3. Description adds no additional meaning beyond the schema's parameter descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description 'Create new webhook' clearly states verb and resource. It differentiates from sibling tools like list_webhooks or create_contact, but lacks specificity about scope or variants.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No guidance on when to use this tool vs other creation tools. Absence of context signals for alternatives like update_webhook (if exists) or usage prerequisites.

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/Cbrown35/mantic-MCP'

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