Skip to main content
Glama
jhliberty

Basecamp MCP Server

by jhliberty

create_webhook

Set up webhooks in Basecamp by specifying a project ID, payload URL, and event types to automate notifications and streamline project management workflows.

Instructions

Create a webhook

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payload_urlYesPayload URL
project_idYesProject ID
typesNoEvent types

Implementation Reference

  • src/index.ts:486-498 (registration)
    Registration of the 'create_webhook' tool including name, description, and input schema in the listTools response.
    {
      name: 'create_webhook',
      description: 'Create a webhook',
      inputSchema: {
        type: 'object',
        properties: {
          project_id: { type: 'string', description: 'Project ID' },
          payload_url: { type: 'string', description: 'Payload URL' },
          types: { type: 'array', items: { type: 'string' }, description: 'Event types' },
        },
        required: ['project_id', 'payload_url'],
      },
    },
  • Input schema definition for the create_webhook tool.
      inputSchema: {
        type: 'object',
        properties: {
          project_id: { type: 'string', description: 'Project ID' },
          payload_url: { type: 'string', description: 'Payload URL' },
          types: { type: 'array', items: { type: 'string' }, description: 'Event types' },
        },
        required: ['project_id', 'payload_url'],
      },
    },
  • Core implementation of webhook creation in BasecampClient class, making the POST API request to Basecamp.
    async createWebhook(projectId: string, payloadUrl: string, types?: string[]): Promise<Webhook> {
      const data: any = { payload_url: payloadUrl };
      if (types) data.types = types;
    
      const response = await this.client.post(`/buckets/${projectId}/webhooks.json`, data);
      return response.data;
    }
  • TypeScript interface definition for Webhook object returned by the createWebhook method.
    export interface Webhook {
      id: string;
      payload_url: string;
      types: string[];
      created_at: string;
      updated_at: string;
    }
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Create a webhook' implies a write operation but reveals nothing about permissions required, whether the creation is idempotent, what happens on failure, rate limits, or the expected response format. For a mutation tool with zero annotation coverage, this lack of behavioral information is a critical gap that could lead to incorrect usage.

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 extremely concise at just three words, with zero wasted language. It's front-loaded with the core action ('Create'), though this brevity comes at the cost of completeness. While under-specified, it's not verbose or poorly structured, earning full marks for conciseness.

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?

Given the complexity of a webhook creation tool (a mutation operation with no annotations and no output schema), the description is incomplete. It fails to address key contextual elements like what the tool returns, error conditions, or how it integrates with the system (e.g., Basecamp, as implied by sibling tools). The high schema coverage helps somewhat, but the overall description lacks the depth needed for safe and effective use.

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%, meaning all parameters (payload_url, project_id, types) are documented in the schema itself. The description adds no additional semantic context beyond what's in the schema—it doesn't explain what a 'payload_url' is used for, what 'project_id' refers to, or what 'types' of events are supported. With high schema coverage, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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

Purpose2/5

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

The description 'Create a webhook' is a tautology that merely restates the tool name without providing any meaningful elaboration. It doesn't specify what kind of webhook is being created (e.g., for what system or purpose), what resources it affects, or how it differs from sibling tools like 'delete_webhook' or 'get_webhooks'. While the verb 'create' is clear, the lack of context makes this minimally informative.

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

Usage Guidelines1/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a project_id), when it's appropriate (e.g., for real-time notifications), or what other tools might be relevant (like 'get_webhooks' to list existing ones or 'delete_webhook' for removal). Without any usage context, an agent would struggle to determine the correct application scenario.

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

Related 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/jhliberty/basecamp-mcp-server'

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