Skip to main content
Glama
Sign In
MCP n8n API Server

MCP n8n API Server

by ahmadsoliman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

call_webhook_get

Executes a GET request to a webhook URL to trigger an n8n workflow or external service.

Instructions

Call a GET webhook

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": {
      "url": "<url>"
    },
    "name": "call_webhook_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe webhook URL to call

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

B3.1/5.0
Behavior2/5

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

No annotations provided to disclose safety or side effects. Description only states action, not behavior like idempotency, timeouts, error handling, or data effects.

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

Conciseness4/5

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

Single, concise sentence. While minimal, it is appropriately sized for a simple tool with one parameter. No unnecessary information.

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 no output schema and minimal description, the tool lacks completeness. No information on return values, URL validation, or behavior expectations.

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 coverage is 100% with parameter 'url' described. Description adds no extra meaning beyond schema, meeting baseline expectation.

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?

Description explicitly states verb 'call' and resource 'GET webhook', clearly differentiating from sibling 'call_webhook_post' by specifying HTTP method.

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 on when to use this tool versus alternatives like 'call_webhook_post' or when not to use it. Lacks context for selecting among siblings.

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