Skip to main content
Glama
Sign In
wp-mcp-control-server

wp-mcp-control-server

by mpierre135
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

wp_delete_form_webhook

Remove a Ninja Forms webhook action by form ID and action ID, stopping unwanted notifications or integrations.

Instructions

Delete a Ninja Forms webhook action

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": {
      "form_id": "<form_id>",
      "action_id": "<action_id>"
    },
    "name": "wp_delete_form_webhook"
  }
}

Input Schema

NameRequiredDescriptionDefault
form_idYesNinja Form ID
action_idYesWebhook action ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.3.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the burden of disclosing the destructive nature of the tool. It does clearly say 'Delete', which signals that the webhook action will be removed, but it adds little beyond that: no mention of irreversibility, cascading effects on the form, cached data, or response behavior. It is honest but minimal.

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?

A single, direct sentence with no filler or redundancy. The core action and resource are front-loaded, making it instantly scannable for an agent.

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

Completeness3/5

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

For a simple two-parameter delete operation, the description and complete schema cover the minimum needed to invoke the tool. However, with no annotations and no output schema, the description omits any indication of success/failure behavior or side effects, which leaves a moderate gap for a destructive operation.

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 the schema already documents both parameters ('Ninja Form ID' and 'Webhook action ID'). The description does not add any additional meaning or clarify parameter relationships, so the baseline score of 3 applies.

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?

The description uses a specific verb ('Delete') and a specific resource ('Ninja Forms webhook action'), clearly identifying the operation. It does not explicitly reference sibling tools like wp_update_form_webhook or wp_list_form_webhooks, but the destructive verb inherently distinguishes it from create/update/list operations.

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 is provided about when to use this tool versus alternatives, no prerequisites are mentioned, and there are no exclusions or context cues beyond the obvious 'delete this resource' implication. The description simply states the action without any decision support.

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