Skip to main content
Glama
FirstReply

FirstReply MCP Server

Official
by FirstReply
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Webhook Update

webhook_update

Update a webhook's target URL or subscribed events by supplying only the fields to change. Use it to redirect deliveries or adjust which FirstReply support events trigger notifications.

Instructions

Update the target URL or events of a webhook. Only provide fields to change.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
eventNoEvent name, or several comma-separated: conversation.create, conversation.update, conversation.delete, conversation.reassign, message.create, message.update, message.delete, contact.create, contact.update, contact.delete, knowledge.create, knowledge.update, knowledge.delete, classification.create, classification.update, classification.delete, template.create, template.update, template.delete, prompt.create, prompt.update, prompt.delete, inbox.create, inbox.update, inbox.delete, member.add, member.remove, organization.update.
targetNoNew target URL.
webhookIdYesThe webhook id (see webhook_list).
organizationIdYesThe organization id. Use organization_list to find it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare the mutation profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so safety is covered. The description adds the partial-update behavior, which is genuinely useful beyond the annotations, but says nothing about permissions, validation of the target URL, or what happens on failure.

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?

Two short, front-loaded sentences with zero redundancy. The partial-update constraint is stated immediately after the purpose.

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 simple four-parameter update tool with fully documented schema and no output schema, the description covers purpose and update mode adequately. Only marginal gaps remain, such as permission requirements and behavior of unset fields.

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 all four parameters are documented in the schema (including the full event enum list and cross-references like webhook_list/organization_list). The description adds the field mapping to target/event but no format or semantics beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb ('Update') and resource ('webhook') plus the two mutable fields (target URL, events). It is clearly distinguishable from webhook_create/delete/list at a glance, though it does not explicitly name or contrast with those siblings.

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?

'Only provide fields to change' conveys patch/partial-update semantics, which is useful context. However, it gives no guidance on when to prefer this over webhook_create, webhook_rotate_secret, or webhook_test, nor any prerequisites for the caller.

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

Deploy Server

Other Tools