Fathom AI MCP Server

Overview Schema Source Related Servers Discussions Admin

create_webhook

Set up a webhook to receive meeting notifications. Choose recording types and include summaries, transcripts, action items, or CRM matches. Returns webhook URL and secret.

Instructions

Create a new webhook for receiving meeting notifications.

At least one of the include_* flags must be true. The webhook will be triggered for the specified recording types and will include the requested content.

Returns the webhook ID, URL, secret (for signature verification), and configuration.

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": {
      "destination_url": "<destination_url>",
      "triggered_for": "<triggered_for>"
    },
    "name": "create_webhook"
  }
}

Input Schema

Name	Required	Description
`triggered_for`	Yes	Array of recording types that trigger this webhook. Options: 'my_recordings', 'shared_external_recordings', 'my_shared_with_team_recordings', 'shared_team_recordings'
`destination_url`	Yes	The URL where webhook events will be sent
`include_summary`	No
`include_transcript`	No
`include_crm_matches`	No
`include_action_items`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses the validation rule (at least one include_* flag), the triggering behavior for specified recording types, and the return value including the secret for signature verification. This adds meaningful behavioral context beyond the schema, though it omits potential side effects or prerequisites.

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 front-loaded with the core purpose in the first sentence. It is compact, containing only four sentences that cover the essential details: purpose, validation constraint, trigger behavior, and return value. No filler or redundancy.

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 has an output schema (so return values are covered), the description is complete for a creation tool. It covers the main action, a key constraint, trigger conditions, and the content included. It does not mention prerequisites like existing meetings or error handling, but these are not critical for basic use and the schema covers parameter specifics.

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 low (33%), with only destination_url and triggered_for described. The description adds value by grouping the include_* flags and stating they control requested content, plus requiring at least one true. However, it does not explain what each flag individually does; their names are self-explanatory, but the description does not explicitly compensate for the low schema coverage.

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 opens with a clear, specific verb and resource: 'Create a new webhook for receiving meeting notifications.' This distinguishes it from sibling tools like delete_webhook and clarifies its domain. The additional details about triggering and return values reinforce the purpose.

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?

The description provides clear context: this is for creating a webhook to receive meeting notifications. It includes a critical usage constraint: 'At least one of the include_* flags must be true.' However, it does not explicitly mention when not to use this tool or name alternatives, such as delete_webhook for removal.

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

Deploy Server