Skip to main content
Glama
aydinfer
by aydinfer

createWebhook

Create webhooks for Spline 3D scenes to map external parameters to scene variables, enabling dynamic content updates and interactive experiences.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sceneIdYesScene ID
nameYesWebhook name
parameterMappingsNoParameter mappings

Implementation Reference

  • Registers the createWebhook MCP tool, including inline Zod schema for inputs (sceneId, name, parameterMappings) and the handler function that constructs webhook data and calls apiClient.createWebhook
    server.tool(
      'createWebhook',
      {
        sceneId: z.string().min(1).describe('Scene ID'),
        name: z.string().min(1).describe('Webhook name'),
        parameterMappings: z.array(z.object({
          paramName: z.string().describe('Parameter name in webhook'),
          variableName: z.string().describe('Spline variable name'),
          variableType: z.enum(['string', 'number', 'boolean']).describe('Variable type'),
        })).optional().describe('Parameter mappings'),
      },
      async ({ sceneId, name, parameterMappings }) => {
        try {
          const webhookData = {
            name,
            ...(parameterMappings && { parameterMappings }),
          };
          
          const result = await apiClient.createWebhook(sceneId, webhookData);
          
          return {
            content: [
              { 
                type: 'text', 
                text: `Webhook created successfully with ID: ${result.id} and URL: ${result.url}` 
              }
            ]
          };
        } catch (error) {
          return {
            content: [
              { 
                type: 'text', 
                text: `Error creating webhook: ${error.message}` 
              }
            ],
            isError: true
          };
        }
      }
    );
  • Handler function for the createWebhook tool. Prepares the webhookData object from the input parameters and invokes apiClient.createWebhook to interact with the Spline API.
    async ({ sceneId, name, parameterMappings }) => {
      try {
        const webhookData = {
          name,
          ...(parameterMappings && { parameterMappings }),
        };
        
        const result = await apiClient.createWebhook(sceneId, webhookData);
        
        return {
          content: [
            { 
              type: 'text', 
              text: `Webhook created successfully with ID: ${result.id} and URL: ${result.url}` 
            }
          ]
        };
      } catch (error) {
        return {
          content: [
            { 
              type: 'text', 
              text: `Error creating webhook: ${error.message}` 
            }
          ],
          isError: true
        };
      }
  • Zod input schema for the createWebhook tool defining required sceneId and name, optional parameterMappings array.
    {
      sceneId: z.string().min(1).describe('Scene ID'),
      name: z.string().min(1).describe('Webhook name'),
      parameterMappings: z.array(z.object({
        paramName: z.string().describe('Parameter name in webhook'),
        variableName: z.string().describe('Spline variable name'),
        variableType: z.enum(['string', 'number', 'boolean']).describe('Variable type'),
      })).optional().describe('Parameter mappings'),
    },
  • Helper method in SplineApiClient that performs the actual API call to create a webhook by POSTing to /scenes/{sceneId}/webhooks
    async createWebhook(sceneId, webhookData) {
      return this.request('POST', `/scenes/${sceneId}/webhooks`, webhookData);
    }
  • src/index.js:91-91 (registration)
    Top-level registration call to registerApiWebhookTools on the MCP server instance, which includes the createWebhook tool.
    registerApiWebhookTools(server);
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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?

Tool has no description.

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/aydinfer/spline-mcp-server'

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